X-Authentication-Warning: new-smtp2.ihug.com.au: Host p37-max11.syd.ihug.com.au [203.173.155.101] claimed to be acceleron
Message-ID: <003001c14741$4beacd10$0a02a8c0@acceleron>
From: "Andrew Cottrell" <acottrel AT ihug DOT com DOT au>
To: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, <sandmann AT clio DOT rice DOT edu>
Cc: <pavenis AT lanet DOT lv>, <djgpp-workers AT delorie DOT com>
References:  <10109261642 DOT AA14453 AT clio DOT rice DOT edu> <2947-Wed26Sep2001203115+0300-eliz AT is DOT elta DOT co DOT il>
Subject: Re: GCC 3.01 and Win 2K Tesing
Date: Thu, 27 Sep 2001 20:43:49 +1000
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Reply-To: djgpp-workers AT delorie DOT com

> > Since 2.04 isn't released yet, I think you should leave it as it is.
> > This might indicate the 2.04 libc needs to be tolerent of "links" done
> > with 2.03?
>
> The ``symlink'' support from older DJGPP version was not removed from
> the current CVS.  It is still supported.
>
> I think the problem is the other way around: whyen, say, a configure
> script says "ln -s foo.c bar.c", v2.04-compiled `ln' creates a
> new-style symlink that GCC compiled with v2.03 cannot grok, so it
> chokes when asked to compile such a file.

Correct I think,  I was using Make built with 2.04 LIBC and as such produced
a new symlink file, but GCC 3.01 was built with 2.03 (with Win 2K patches).
As expected.

In the next few weeks when time permits I will try to build GCC 3.01 with
the 2.04 LIBC and put it on clio. A timeframe for me to do this would be
anywhere between 2 and 3 weeks time.

Andrew