From: kagel AT quasar DOT bloomberg DOT com
Date: Thu, 23 Jan 1997 11:58:15 -0500
Message-Id: <9701231658.AA07128@quasar.bloomberg.com >
To: indrek AT warp DOT edu DOT ee
Cc: djgpp AT delorie DOT com
In-Reply-To: <Pine.LNX.3.95.970122234703.2206A-100000@warp.edu.ee> (message from Indrek Mandre on Wed, 22 Jan 1997 23:53:20 +0200 (EET))
Subject: Re: getopt_long lost?
Reply-To: kagel AT dg1 DOT bloomberg DOT com

   Errors-To: postmaster AT ns1
   Date: Wed, 22 Jan 1997 23:53:20 +0200 (EET)
   From: Indrek Mandre <indrek AT warp DOT edu DOT ee>
   Mime-Version: 1.0
   Content-Type: TEXT/PLAIN; charset=US-ASCII
   Content-Length: 374


   Hi!
   I was porting some days ago one gnu tool from linux to djgpp and I ran
   in trouble with funcsion getopt_long, I didn't find it in djgpp.
   Is it supposed to be so? Do I have to get it from some linux
   libc source? Any comments?
   Pure getopt is and seems to work perfectly.

Get GNU getopt library source from the FSF.  IMHO it is not covered by GPL but 
the source will specify.  This is a subfunction of GNU getopt to handle long
option names.  It is user callable though #defines usually control the use of 
this option at compile time.

-- 
Art S. Kagel, kagel AT quasar DOT bloomberg DOT com

A proverb is no proverb to you 'till life has illustrated it.  -- John Keats