From:	pavenis AT lanet DOT lv
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Mon, 26 Jun 2000 15:21:39 +0200
MIME-Version:	1.0
Subject:	Re: GCC and the rest of us, again
Message-ID:	<39577503.28081.74B5D1@localhost>
In-reply-to:	<Pine.SUN.3.91.1000626154721.7682I-100000@is>
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

On 26 Jun 2000, at 15:54, Eli Zaretskii wrote:

> For the recent round of GCC-maintainers-vs-the-rest-of-the-world series, 
> read the thread "Re: gcc compiles assert() to code that requires linking 
> with gcc" on bug-gcc AT gnu DOT org.
> 
> For those who don't know: Martin Buchholz, whose message started that 
> thread, is a maintainer of XEmacs, and one of the nicest people I've 
> ever met.

Here is example of this problem with gcc-2.95.2

When I'm building gcc-2.95.2 as native compiler for DJGPP under 
Linux libgcc.a is built using cross-compiler and as result _eprintf
is left out (--inhibit-libc forced when cross-compiling). No clean way 
how to override this is provided (except than editting gcc/libgcc2.c). 
g77 uses assert with _eprintf and as result one have to modify 
manually libgcc2.c to build G77 using cross-compiler. All cases when 
host!=build suffers from that

Andris
 

- Raw text -