Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 29 Nov 1998 12:37:38 +1030
From:      Greg Lehey <grog@lemis.com>
To:        Andrew <andrew@violet.org>, questions@FreeBSD.ORG
Subject:   Re: /usr/lib/crt0.o & freebsd 3.0-release
Message-ID:  <19981129123738.V6182@freebie.lemis.com>
In-Reply-To: <19981128174357.A3586@apogee.whack.org>; from Andrew on Sat, Nov 28, 1998 at 05:43:57PM -0800
References:  <19981128174357.A3586@apogee.whack.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday, 28 November 1998 at 17:43:57 -0800, Andrew wrote:
> Hello all,
>
> Upon installing freebsd 3.0-release and trying to
> compile gcc-2.8.1, I find that /usr/lib/crt0.o is
> missing/moved to either /usr/lib/aout/crt0.o -or-
> /usr/lib/crt1.o
>
> Which one should I use...

The linker will decide for you.

> Is this fixed in 3.0-current...

There's nothing to fix:

$ file /usr/lib/crt1.o /usr/lib/aout/crt0.o 
/usr/lib/crt1.o:      ELF 32-bit LSB relocatable, Intel 80386, version 1 (FreeBSD), not stripped
/usr/lib/aout/crt0.o: FreeBSD/i386 object not stripped

If you're linking an a.out executable, the linker will choose
/usr/lib/aout/crt0.o.  If you're linking an ELF executable, the linker
will choose /usr/lib/crt1.o.

> Now i am wondering what else is going to cause gcc
> to fail to compile? (Actually, this is the first
> OS I have ever run where, out of the box, gcc would
> not compile... ouch!)

It looks like you're describing a possible (but incorrect) reason for
a problem you haven't described.

Greg
--
See complete headers for address, home page and phone numbers
finger grog@lemis.com for PGP public key

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message



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