This is the mail archive of the firstname.lastname@example.org
mailing list for the Cygwin project. See the Cygwin
home page for more information.
Re: problem building egcs-1.1.2
- To: email@example.com, firstname.lastname@example.org
- Subject: Re: problem building egcs-1.1.2
- From: N8TM@aol.com
- Date: Fri, 26 Mar 1999 01:29:06 EST
In a message dated 3/25/99 9:51:27 PM Pacific Standard Time, email@example.com
> Has anyone else attempted building egcs-1.1.2 with
> Mumit's patches, and with what success?
I set the compiler flags as follows
export CFLAGS='-Os -malign-double'
export CXXFLAGS='-Os -malign-double'
export BOOT_CFLAGS='-Os -malign-double -pipe'
and symlinked all the include files to /usr/include
I gzipped the texinfo source so that it would not be configured into the
build, as that is broken at present.
On NT4/SP3, with standard cygwin-b20.1, I used
On W95/OSR25, with cygwin snapshot binaries through 19990307, I used
make LANGUAGES='c c++ f77' bootstrap-lean
as the testsuite never gets to gcov, objc, or java, and chill does not
configure for cygwin, followed by
make -k LANGUAGES='c c++ f77' install
I believe under NT it is necessary to configure libf2c separately, and the W95
build stalls after building tmplibgcc2.a, so I do
'mv gcc/tmplibgcc2.a libgcc2.a'
and resume the bootstrap.
For everything I've tested, the gcc/g++/g77 built on NT behave the same as the
binaries from Mumit's site. For the newer snapshot configuration, the g++/g77
built on W95 avoid the conflicts between the older and newer CTYPE schemes but
otherwise behave the same as Mumit's distribution.
The process takes around 4 hours on NT, and about 2 on W95, with 200 Mhz cpus.
I haven't seen any comparison failures; those most likely arise from switching
compilers or options between stages.
The gcc-1.1.2 built on NT is able to build the current egcs snapshots; on W95
I haven't been able to get it configured so that the snapshot xgcc finds all
necessary include files.
Want to unsubscribe from this list?
Send a message to firstname.lastname@example.org