Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 19 Jan 1998 11:34:34 -0800 (PST)
From:      Timothy Moore <moore@WOLFENET.com>
To:        garbanzo@hooked.net
Cc:        sos@FreeBSD.ORG, hackers@FreeBSD.ORG
Subject:   Re: elf and -current
Message-ID:  <199801191934.LAA06191@gonzo.wolfenet.com>
In-Reply-To: <Pine.BSF.3.96.980119105204.382G-100000@zippy.dyn.ml.org> (message from Alex on Mon, 19 Jan 1998 10:52:43 -0800 (PST))

next in thread | previous in thread | raw e-mail | index | archive | help
   Date: Mon, 19 Jan 1998 10:52:43 -0800 (PST)
   From: Alex <garbanzo@hooked.net>

   On Mon, 19 Jan 1998, Søren Schmidt wrote:

   > Why on earth would you want to use gcc-2.8 ??
   > Getting tha system ELF'ified is errorprone enough, you dont need extra
   > "help" from a new (potentially) buggy compiler....

   I don't know about Amancio, but I "ELF'ified" to get egcs support, and
   purposely avoided gcc 2.7.x due to C++ problems.  The elfkit itself was
   very slick, however, two or three things should probably be addressed.

Ditto.

   1.) So far only FSF gcc will work as a cross compiler (not elf to elf, but
	   a.out to elf), egcs bombs out here.

I managed to build egcs as a cross compiler, following the
instructions in the elfkit's README.  I used binutils-2.8.  I had to
hide the limits.h in egcs' privite include directory in order to
compile libc; BSD defines some Posix constants in there that aren't in
the GNU version.

   2.) The shared libc depends on the crt* code, and the crt* code depends on
	   the static libc.
   3.) The crt* code seems to be missing a few symbols that libc uses.
	   However it's probably missing a few more.  Anyone care to fill me
	   in as to which ones are missing?

What are the symptoms of this?  My egcs seemed to do alright on the
gcc test suite, modulo problems caused by a buggy elf-lorder (I had
assumed that the lorder bugs described in the README had been fixed in
binutils-2.8;  they haven't) and FreeBSD floating point exception
behavior. The g++ test suite had a bunch of unexpected failures, but I
can imagine these have the same cause.  I'll check into those tonight
after I rebuild libc with the fixed lorder.

Tim



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801191934.LAA06191>