On Dec 10, 2007, at 21:40, Michael Hart wrote:
On 11/12/2007, at 2:16 PM, Michael Hart wrote:
And then you'll no doubt run into the problem outlined in Ticket
#13472:
http://trac.macports.org/projects/macports/ticket/13472
I haven't tried the solution listed there, but hopefully that
works for you.
There's actually a couple of small typos in the Trac Ticket comment
re the symlinks (the /bin/* files incorrectly named). This worked
for me:
ln -s /opt/local/include/libguile16 /opt/local/include/libguile && \
ln -s /opt/local/include/libguile16.h /opt/local/include/libguile.h
&& \
ln -s /opt/local/include/guile16 /opt/local/include/guile && \
ln -s /opt/local/bin/guile16 /opt/local/bin/guile && \
ln -s /opt/local/bin/guile16-config /opt/local/bin/guile-config && \
ln -s /opt/local/bin/guile16-snarf /opt/local/bin/guile-snarf && \
ln -s /opt/local/bin/guile16-tools /opt/local/bin/guile-tools && \
ln -s /opt/local/lib/libguile16.a /opt/local/lib/libguile.a && \
ln -s /opt/local/lib/libguile16.dylib /opt/local/lib/libguile.dylib
&& \
ln -s /opt/local/lib/libguile16.la /opt/local/lib/libguile.la
(trying to add this to Trac too, but having problems logging in)
Ugh. The guile16 port deliberately installs things with the version
suffix appended so that guile and guile16 can be installed
simultaneously. Making symlinks as you've described completely
contradicts that goal.
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users
