Le 07-04-09 à 20:35, Ken McGaugh a écrit :
Hi all,
I have just recently started to use macports under OSX and I am
replacing all my manually installed libraries/tools
with ones installed via macports. I've run into many problems with
the fltk-1.1.7 port...
1. It crashes with a bus error. If I build it manually it works
OK. I think this is related to the following issues.
2. It is built as an x11 library even though it places the
resulting "fluid" application into /Applications/MacPorts/fltk
and asks you to bless the file with "fltk-config --post",
both of which imply it should be a native aqua application.
3. It isn't built with --enable-threads which is needed by quite
a few apps.
4. It depends on many libraries which come with OSX, but forces
you to build redundant versions of them through macports.
In my brief experience with macports it seems that fltk needs to
have multiple variants to handle the above issues. One
of my questions is that should the base variant of fltk be the x11
version or should it be aqua with the variant being x11?
Absolutely. This is a really silly error. The fact that it is
listed as a x11 port dos not change anything else than being confusing.
Also, is there a way to dynamically have macports know if
preinstalled versions of libraries exist and use them instead?
There is, but it often turns out to be a bad idea. If it helps
making the port work, then that is another story.
yves
_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo/macports-users
