llvm-gcc42's libgcc_s.1.dylib

[Ryan Schmidt]

If llvm-gcc42 is installed, practically any port built thereafter  
will link to its libgcc_s.1.dylib in ${prefix}/lib rather than  
Xcode's in /usr/lib, which obviously causes those ports to blow up if  
I then later uninstall or deactivate llvm-gcc42, since none of those  
ports declare (nor should declare) dependencies on llvm-gcc42. Should  
llvm-gcc42 rename its libgcc_s.1.dylib (and if so would software that  
requires llvm-gcc42 still work?) or is there another solution anyone  
can think of?