X-Authentication-Warning:	delorie.com: mail set sender to djgpp-workers-bounces using -f
From:	<ams AT ludd DOT ltu DOT se>
Message-Id:	<200410291614.i9TGEdwM013121@speedy.ludd.ltu.se>
Subject:	Re: Fix for environ pollution
In-Reply-To:	<200410291255.10316.pavenis@latnet.lv> "from Andris Pavenis at Oct
	29, 2004 12:55:10 pm"
To:	djgpp-workers AT delorie DOT com
Date:	Fri, 29 Oct 2004 18:14:39 +0200 (CEST)
X-Mailer:	ELM [version 2.4ME+ PL78 (25)]
MIME-Version:	1.0
X-ltu-MailScanner-Information:	Please contact the ISP for more information
X-ltu-MailScanner:	Found to be clean
X-MailScanner-From:	ams AT ludd DOT ltu DOT se
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

According to Andris Pavenis:
> If we don't have _environ defined in libc.a then GCC versions using own copy
> of linker script will break.

Isn't this what you risk if you aren't using what the target system
provides?

I'm not complaining as I don't understand _why_ gcc must have its own
version; but there probably are some profound reason why. (And you,
Andris, don't have to explain why.)

> I can put linker script from current CVS of DJGPP 
> in next releases og GCC for DJGPP, but it still will break for those who are 
> using earlier versions. 

Well, as it looks like latest DJGPP will require gcc 3.something or
later, why can't gcc 3.whatever require DJGPP 2.04 beta or later?


Right,

						MartinS

- Raw text -