On Jun 13, 2009, at 04:15, Jeremy Lavergne wrote:
On Jun 13, 2009, at 5:06 AM, Ryan Schmidt wrote:
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?
Could block llvm's location from the path unless it's depended
upon? Something akin to trace mode?
I was hoping there was something simple that could be done, say in
the llvm-gcc42 port, rather than a change that would have to be made
to MacPorts base to accommodate the issue. But I don't know what that
solution might be, so maybe your suggestion is the way to go.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
