Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<19990629121558.21248.rocketmail@web105.yahoomail.com>
Date:	Tue, 29 Jun 1999 05:15:58 -0700 (PDT)
From:	Earnie Boyd <earnie_boyd AT yahoo DOT com>
Reply-To:	earnie_boyd AT yahoo DOT com
Subject:	Re: undefined references when compiling with -mno-cygwin
To:	cygwin AT sourceware DOT cygnus DOT com
MIME-Version:	1.0

--- Dirk Fieldhouse <fieldhouse AT logica DOT com> wrote:
> On Mon, 28 Jun 1999 17:55:17 +1300, Ross Smith <ross DOT s AT ihug DOT co DOT nz> wrote: 
> >Mumit Khan wrote:
> >>
> >> On Fri, 25 Jun 1999, Jeff Boleng wrote:
> >> >
> >> > [ on compiling without cygwin dll ]
> >> >
> >> > I didn't find anything in the FAQ or archives, so if anyone can help
> please
> >> > let me know.
> >>
> >> You're kidding, right? There're tons of posts regarding mno-cygwin in the
> >> archives, and some of these deal with precisely this issue. Please at
> >> the very least see my mno-cygwin howto at:
> >>   http://www.xraylith.wisc.edu/~khan/software/gnu-win32/
> 
> >He's got a point about the FAQ, though. It just says to use the
> >-mno-cygwin flag, with no hint that anything more is required. >That's
> seriously misleading, and is undoubtedly why so many people >keep asking
> about this. Why not put a pointer in there?
> >
> >...
> 
> For instance it would be nice to clarify whether it's necessary to maintain
> two entirely separate sets of lib*.a for linking with the two styles of
> build. As I understand it there should be on the cygwin hand
> 
> *crt*.o for cygwin, libcygwin.a, (?)
> 
> and on the other
> 
> *crt*.o for mingw32, libcrtdll.a/libmsvcrt*.a, (?)
> 
> It seems, borne out by experience, that lib*.a for Windows DLLs should be
> interchangeable - since they're only calling the DLL entry points - but any
> lib that contains statically linkable code calling cygwin-only entry points
> or dependent on cygwin semantics through conditional compilation obviously
> won't be.
> 
> I wonder which those might be - libgcc.a presumably? Do/should such libs all
> reside in the appropriate gcc target/version directory?

I suggest that anyone wishing to see the FAQ changed submit the changes
formally to this list so that they can get incorporated into the FAQ.  Yes,
statements made to this list often can be found in the FAQ.
===
Earnie Boyd <mailto:earnie_boyd AT yahoo DOT com>

Newbies, please visit
<http://www.freeyellow.com/members5/gw32/index.html>

(If you respond to the list, then please don't cc me)
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -