Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!brutus.cs.uiuc.edu!coolidge
From: coolidge@casca.cs.uiuc.edu (John Coolidge)
Newsgroups: comp.unix.aux
Subject: Re: -The weirdness of the crt*.o files-
Message-ID: <1990Jul31.233032.18984@brutus.cs.uiuc.edu>
Date: 31 Jul 90 23:30:32 GMT
References: <43470@apple.Apple.COM>
Sender: news@brutus.cs.uiuc.edu
Reply-To: coolidge@cs.uiuc.edu
Organization: U of Illinois, CS Dept., Systems Research Group
Lines: 21

abyss@Apple.COM (Ananthan Srinivasan) writes:
>To see all the right crt*.o files that need to be used to keep 'ld' happy,
>write a dummy program (dummy.c) and compile it using "cc -v".
>On A/UX 2.0 you will see that 'ld' is invoked as foll:
>"/bin/ld /lib/crt1.o /lib/crt2.o dummy.o -lc /lib/crtn.o /usr/lib/shlib.ld"
>On A/UX 1.* this is
>"/bin/ld /lib/crt0.o dummy.o -lc /usr/lib/shared.ld".

This is basically how I determined what to have gcc use in its
run of ld. The gcc patches that I just released, and the 1.37.91
binaries, use crt1, crt2, crtn, and shlib.ld whenever building
an executable. The g++ patches (that I'll hopefully get out the
door soon :-)) will also use them.

--John

--------------------------------------------------------------------------
John L. Coolidge     Internet:coolidge@cs.uiuc.edu   UUCP:uiucdcs!coolidge
Of course I don't speak for the U of I (or anyone else except myself)
Copyright 1990 John L. Coolidge. Copying allowed if (and only if) attributed.
You may redistribute this article if and only if your recipients may as well.