From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10301251938.AA26309@clio.rice.edu>
Subject: v2.03 crt0 + v2.04 libc compatibility
To: djgpp-workers AT delorie DOT com
Date: Sat, 25 Jan 2003 13:38:11 -0600 (CST)
In-Reply-To: <9003-Sat25Jan2003195735+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Jan 25, 2003 07:57:35 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> > 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.

If we want, this is fixable by putting these symbols in their own
modules in the v2.04 libc.  I had moved them to crt0 since it
required them and managed them.

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 ...