From: sandmann AT clio DOT rice DOT edu (Charles Sandmann) Message-Id: <10301261735.AA20764@clio.rice.edu> Subject: Re: v2.03 crt0 + v2.04 libc compatibility To: djgpp-workers AT delorie DOT com Date: Sun, 26 Jan 2003 11:35:10 -0600 (CST) In-Reply-To: from "Eli Zaretskii" at Jan 26, 2003 08:22:07 AM 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 > > 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. > > 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. The V2.04 libc does (and so does the V2.03 crt0 for that matter) - and they aren't defined in either (they are now defined in v2.04 crt0). I probably never see problems because when I'm working in my CVS tree I set LIBRARY_PATH and C_INCLUDE_PATH.