On Wed, Dec 16, 2009 at 09:04:13PM -0600, Ryan Schmidt wrote:
> My recommendation is to not install llvm-gcc42 until this issue is resolved.
> If anyone can assist in resolving this issue, it would be appreciated.
Isn't the solution to both of these problems (libiberty & libgcc_s) just a
matter of adding
--libdir=${prefix}/lib/${name}
--libexecdir=${prefix}/libexec/${name}
--includedir=${prefix}/include/${name}
to configure.args?
(I don't use llvm-gcc at all myself, but in my experience this is
typically the answer to such problems with gcc.)
Dan
--
Dan R. K. Ports <[email protected]>
Research Henchman
Massachusetts Institute of Technology <[email protected]>
Computer Science and Artificial Intelligence Lab <[email protected]>
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
