Date:	Sun, 26 Jan 2003 08:22:07 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	djgpp-workers AT delorie DOT com
Subject:	Re: v2.03 crt0 + v2.04 libc compatibility
In-Reply-To:	<10301251938.AA26309@clio.rice.edu>
Message-ID:	<Pine.SUN.3.91.1030126081518.28101C-100000@is>
MIME-Version:	1.0
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

On Sat, 25 Jan 2003, Charles Sandmann wrote:

> > > Since various things have been moved around in the start-up code,
> > > the Cygnus test suite no longer links, because it cannot resolve
> > > all the symbols. 2.04 libc is not compatible with 2.03 crt0.
> > 
> > Could you please tell more about the problems and show us the
> > relevant error message(s) you get during the build?
> 
> V2.03 stub and V2.04 libc are not compatible because of the 
> symbols I moved.  V2.03's stub does not contain djgpp_ds_alias or
> crt0_startup_flags - so it either can't find them or tries to
> pull them from the v2.03 libc, which then causes other conflicts.

Thanks for the reminder.

However, I still don't understand why did this affect the test suite.  
IIRC, it doesn't use the DS alias; as for the startup flags, I'm not 
sure, but I thought it didn't use them either.

> But I do think it's weird that we would be getting the two mixed up
> during linking - probably better that the error happens so we know
> something bad has happened ...

The Cygnus test suite was set up to use libm.a from the source tree, but 
link in ``the usual libc.a''.  I don't remember why did I do that, so I'd 
like to understand the issues before we decide about the change.

One possible issue is whether we want djtstNNN.zip be usable without 
djlsrNNN.zip.

- Raw text -