🚀 go-pugleaf

From alt.sys.sun:
    From: ken@syd.dit.CSIRO.AU (Ken.Yap)
    Newsgroups: alt.sys.sun
    Subject: Re: avoiding gcc-ld with gcc
    Date: 4 Aug 91 23:55:35 GMT
    Organization: CSIRO Division of Info Tech, Sydney, Australia

    >Don't know what you were expecting, but I doubt it will work for the
    >above case.  The problem is that Sun's ld won't work with object code
    >created by g++, you have to use gcc-ld.  But, as was pointed out, gcc-ld
    >does not handle shared libraries, so when compiling with gcc it's better
    >to use the standard ld.  What this means is that you have to have some
    >way to tell g++ to use gcc-ld while keeping gcc from using it, but they
    >both use the exact same method to determine which ld to use.  Mainly,
    >check to see if gcc-ld exists, and if so, use it.
    >
    >To fix the problem here I changed the g++ front end to look for g++-ld
    >and use it, and put gcc-ld in /usr/local/lib as g++-ld.  Not a real
    >elegant solution, but one that works.

    That is correct. g++ requires gcc-ld, not /bin/ld. Here I solved the
    problem by

	    ln -s /bin/ld /usr/local/lib/ld

    and

	    gcc ... -B/usr/local/lib/ ...

    This causes /bin/ld to be used in preference to gcc-ld. The reason I
    don't just say -B/bin/ is so as not to get /bin/as. Perhaps it might be
    better to get g++ to call g++-ld, and then gcc-ld can be a link to
    /bin/ld.
--

-- Ethan (ethanb@u.washington.edu)