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:	<199905291719.MAA18160@mercury.xraylith.wisc.edu>
To:	Brian Macy <bmacy AT sunshinecomputing DOT com>
cc:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: Building EGCS for MingW32 from CVS...
In-Reply-To:	Your message of "Sat, 29 May 1999 00:27:01 PDT."
	<374F96C5 DOT A19F1409 AT sunshinecomputing DOT com>
Date:	Sat, 29 May 1999 12:19:38 -0500
From:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

Brian Macy <bmacy AT sunshinecomputing DOT com> writes:
> Thanks for the info... it unfortunately doesn't work. Actually building
> a native Linux egcs compiler fails itself... dies on objc/objc.h on the
> second compile pass and has for quite some time. With the Win32
> cross-compiler is fails in many locations and finally dies (after some
> minor tweaks here or there) on libgcc2.a trying to process the assembly
> files produced for _multi, etc.

Hmmm ... My CVS egcs tree is updated once a day and I build Linux, x-Mingw 
and x-Cygwin compilers a few times a week. Just built it last night and
all 3 worked. This is without any of my local patches (I maintain separate
CVS repositories), so that's not the reason why mine works. You should 
right away report any problems you had building a linux compiler to 
egcs-bugs AT egcs DOT cygnus DOT com.

Without more information, I'm afraid I can't help with your problem. Info
such as exact configure options, how you've setup the cross-environment
(copied the includes and libs to the right places?), etc would be useful.
Also, `fails in many locations and finally dies' is rather imprecise.

I assume you already have cross-binutils installed (i386-mingw32-as,
i386-mingw32-ld, i386-mingw32-ar, i386-mingw32-ranlib, etc).

Did you run ``cd gcc; make installdirs'' when building the cross compilers?
That's needed to get the includes relative to the gcc compiler installation
directory.

> Oh well... hopefully I can get my hands on a newer binary distribution
> sometime soon. Currently Borland C++, Borland Builder, and Linux egcs
> out of CVS are the only compilers that can handle the template libraries
> I use. I assume Win32 egcs for MingW32 out of CVS would also handle it.
> Visual C++ 5.0 (with and without SP3) doesn't handle it... I'll be
> trying VC++ 6.0 SP3 and Watcom 11.0a this next week. It's pretty
> impressive that egcs 1.1.2 for MingW32 handles the templates almost
> identically as well (or poorly) as Visual C++ 5.0 SP3 and much better
> than VC++ 5.0 without service packs.

egcs-1.1.2 is way ahead of VC 6 in template handling (VC of course has a
much more compliant C++ standard library, so you gain some and lose some). 
I know nothing about Watcom or C++ Builder (I hear very good things about 
Builder however).

Regards,
Mumit


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

- Raw text -