Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Date:	Wed, 28 Nov 2001 20:20:08 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: which getopt.c is cygwin1.dll using?
Message-ID:	<20011129012008.GE9605@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<200111282125 DOT NAA27019 AT cygnus DOT com>
Mime-Version:	1.0
In-Reply-To:	<200111282125.NAA27019@cygnus.com>
User-Agent:	Mutt/1.3.23.1i

On Wed, Nov 28, 2001 at 02:25:19PM -0700, Mark Paulus wrote:
>I just pulled the source for cygwin-1.3.5-3 and see that there are 3
>different copies/versions of getopt.c, 1 of getopt1.c and a
>getoptlong.c So, when I do a getopt in my piece of code, which
>copy/flavour/version of getopt am I going to invoke??

Why not apply Occam's razor to the problem?

There's a getopt.c in a directory called 'libiberty'.
There's a getopt.c in a directory called 'newlib'.
And, there's a getopt.c in a directory called 'cygwin'.

Now, which of the above would you assume would be incorporated into
cygwin1.dll?

Or, you could even look in the Makefile if this kind of analysis makes
no sense.

>I need to track down an issue, but I would like to get it done while I
>am still a relatively young man....

Next step will be to figure out whether to use vim or vi, I suppose.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -