On Jun 18, 2009, at 4:06 PM, Daniel J. Luke wrote:
On Jun 18, 2009, at 5:17 AM, Boey Maun Suang wrote:
Consequently, I can't see any relative location to which we can
extract a GCC bootstrap, and /var/tmp is the best absolute path
that I can think of for this purpose.
Incidentally, I used otool on the executables in the current ghc
bootstrap compiler, and they contain _absolute_ references to /opt/
local/lib/libgmp.3.dylib, so for those who try to install MacPorts
ghc and who have configured ${prefix} to be other than /opt/local,
the build will either fail due to the non-existence of /opt/local/
lib/libgmp.3.dylib, or (in accordance with the dyld(1) man page's
description of the DYLD_LIBRARY_PATH and DYLD_FALLBACK_LIBRARY_PATH
variables), it will silently pick up libgmp.3.dylib in another
location, such as /usr/local/lib, when it is run. I haven't looked
into it, but we may find that the ghc bootstrap actually has this
same problem, just not in such an obvious or severe form.
As always, your thoughts (and those of others on the list) would be
appreciated.
If it's just the libraries in the bootstrap compiler that are a
problem, then you could do the temp install into somewhere like $
{worksrcpath} and set DYLD_FALLBACK_LIBRARY_PATH ...
--
Daniel J. Luke
Daniel:
I understood Boey Maun Suang to be saying the paths had to be hard
coded, and /var/tmp was the only thing he could rely on to be the same
on all machines.
William Davis
frstanATbellsouthDOTnet
Mac OS X.5.7 Darwin 9.7.0
XQuartz 2.4.0 (xorg-server 1.5.3-apple8)
Mac Mini Intel Duo @ 1.86 GHz
Mundus vult decepi, ego non
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
