Delivered-To: listarch-cygwin AT sourceware DOT cygnus DOT com
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: <199902082149.PAA11179@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: LOCALHOST.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: Juergen Lock <nox AT jelal DOT kn-bremen DOT de>
cc: gnu-win32 AT cygnus DOT com
Subject: Re: cross compiler build fail (multiple definition of `fhandler_base::get_native_name(void)', and more) 
In-reply-to: Your message of "Mon, 08 Feb 1999 21:57:18 +0100."
             <199902082057 DOT VAA04596 AT saturn DOT hb DOT north DOT de> 
Date: Mon, 08 Feb 1999 15:49:51 -0600
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Juergen Lock <nox AT jelal DOT kn-bremen DOT de> writes:
>  Thanx!  Do i need egcs, how is it better than the vanilla gcc that
> comes with the dev-src.tar.bz2?  I didnt know about the CROSS directory,
> did everything in the `root' directory (.../src) until now
> (had to symlink Makefile.in from .. btw)

Yes, egcs. My instructions quite possibly will not work with vanilla/FSF
GCC.

>  I have re-started from scratch in CROSS now but still got a link problem
> (see below).
> 
> > Also, the target is i586-cygwin32, not i386-unknown-cygwin32; you need
> > this for various reasons.
> 
>  Umm.  Does that mean the target machine cant be a 486?  or would
> i486-cygwin32 also work?

Please use what I suggest -- egcs and i586-cygwin32 as the target name,
and then I'll take a look at the errors if any. 

Re your subscription to the mailing list, see Cygnus home page at
http://sourceware.cygnus.com/cygwin/ for more info. The mailing lists
have recently changed, so perhaps your subscription didn't go through?

Regards,
Mumit


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