This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What is the future of gcc-2.95.3-prerelease ?
- To: "David Korn" <dkorn at pixelpower dot com>, <tprinceusa at mindspring dot com>
- Subject: Re: What is the future of gcc-2.95.3-prerelease ?
- From: "Tim Prince" <tprince at computer dot org>
- Date: Fri, 16 Feb 2001 21:50:12 -0800
- Cc: <gcc at gcc dot gnu dot org>
- References: <718D38CAB6E0D011B2C90060970C28A56426C7@EXCHANGESERVER>
----- Original Message -----
From: "David Korn" <dkorn@pixelpower.com>
To: <tprinceusa@mindspring.com>
Cc: <gcc@gcc.gnu.org>
Sent: Friday, February 16, 2001 4:53 AM
Subject: RE: What is the future of gcc-2.95.3-prerelease ?
> >-----Original Message-----
> >From: tprinceusa@mindspring.com [mailto:tprinceusa@mindspring.com]
> >Sent: 15 February 2001 21:56
>
> >[SNIP!] However, I haven't been able to
> >build 2.95.3 in cygwin, while 2.97 is doing well there.
>
> I've had no problems building 2.95.3 cross compilers under cygwin. What
> goes wrong for you? Is it a bootstrap problem?
>
> DaveK
Thanks for the reminder. With the current cygwin1-20010213.dll, remembering
how 2.95 has to be treated as a cross compiler build even when host and
target are the same, I got gcc-2.95.3 to bootstrap. I got an excellent g77
out of it by hacking around the obstacles in that version of libf2c (it
doesn't find include files in the standard places under cygwin, and
[de]time_.c are consistent only with cygwin-b20, a version which no one
runs). It's probably better simply to substitute the current libf2c, which
is no different except for bug fixes. I think it would be too much work to
find a way to have satisfactory g++ and g77 from the same build. The g++ I
built passed about 50% of the libio and libstdc++ tests; not good enough.