🚀 go-pugleaf

In article <JNREES.92Apr30084121@tofu.mit.edu>, jnrees@athena.mit.edu (Jim Rees) writes:

|> 
|> I wanted an ANSI compiler for the Sun4's I work on, so I got gcc-2.1.
|> When I realized this didn't give me all the ANSI header files I
|> needed, I then fetched glibc-1.03.  The documentation for glibc
|> strongly recommends using GNU ld, but I'm not sure if I've got this or
|> not.  A file named ld gets created by install-collect2 in the gcc
|> Makefile, but I didn't plan on using C++ or Objective C, so I didn't
|> run this.  Is *this* GNU ld, or is it something else?  
|> 
|> 	Jim

The following comments relate to gcc2.x for sparcs. Your mileage may vary.

The ld created by install-collect2 is a wrapper for another linker. The is usually
the system ld or GNU's linker, gld. gld is part of the binutils distribution from
FSF. You do not need to run install-collect2 if you are just building C systems.
It is required for C++. I don't know about Objective-C. Supposedly you can use
gld without collect2. gld does resolve static constructors correctly but it gets
a little flakey when it comes to dealing with shared libraries. I haven't had the
chance to file a bug report yet. Using the collect2 ld and letting it call the system
ld seems to work fine. I'd rather just gld, but it ain't quite there yet.


Ross Huitt
bytor@ctt.bellcore.com