From: pavenis AT lanet DOT lv To: "Eli Zaretskii" Date: Fri, 22 Jun 2001 13:58:57 +0300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: gcc 3.0 released Cc: djgpp-workers AT delorie DOT com Message-ID: <3B334F21.5415.EB76DE@localhost> In-reply-to: <9003-Fri22Jun2001110259+0300-eliz@is.elta.co.il> References: (message from Andris Pavenis on Fri, 22 Jun 2001 08:25:34 +0300 (WET)) X-mailer: Pegasus Mail for Win32 (v3.12c) 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 Precedence: bulk On 22 Jun 2001, at 11:03, Eli Zaretskii wrote: > > Date: Fri, 22 Jun 2001 08:25:34 +0300 (WET) > > From: Andris Pavenis > > > > True. Anyway using the same name may cause problems if one unzips > > djdev203.zip after gcc30b.zip. > > Then let's update djdev203.zip on SimTel.NET with djgpp.djl from CVS. > Then the only users who will be left with the old linker script are > those who already have it installed. > > > I'm going to install it > > with gcc30b.zip in lib/gcc-lib/djgpp/3.0 so even if we'll have to do that > > some more time in future there will be no need to change name any more > > Please don't. I don't want to have one more unknown when I debug > users' problems from across the ocean. It is hard enough as it is. I'm going to use a different name so it's impossible gcc will take incompatible one from djdev203.zip unless somebody will mess with specs. I'm sure having 2 incompatible files with the same name is going to cause more problems rather than temporary changing the name (up to time when we'll be able to require users to install djdev204.zip or above). What I suggesting is to temporary use linker script with a slightly different name before djdev204.zip will be released Andris