[patch] build fat libgcc_s.1.dylib for darwin

[Mike Stump]

On Jul 10, 2006, at 4:04 PM, Eric Christopher wrote:
>>> +    $(LN_S) $(DESTDIR)$(slibdir)/libgcc_s.1.dylib \
>>> +        $(DESTDIR)$(slibdir)/libgcc_s_ppc64.1.dylib
>> No.  symlinks should always be the shortest, most direct possible.
>> I think that means:
>>> +    $(LN_S) libgcc_s.1.dylib \
>>> +        $(DESTDIR)$(slibdir)/libgcc_s_ppc64.1.dylib
>> ?
>
> After my previous pain with symlinks in this process I think that  
> keeping it as specific as possible would be best.

No, that's wrong.  That's wrong because when relative methods are  
used to find the libraries, the wrong library is then found.  This  
would also break an existing, working feature, that isn't  
acceptable.  That feature is the ability to move the entire  
installation around and have it `just work'.

If you tried it, you'd discover that this link would not point to  
your file, but rather to a randomly different file.

> Works for me with make -j3 and make -j2

Excellent.