Ryan Schmidt wrote:
libtool is usually built in the build directory by running configure, it is included in the package. I had a quick look at the bugs mentioned:
http://trac.macosforge.org/projects/macports/ticket/13653 http://trac.macosforge.org/projects/macports/ticket/13648
In both cases an installed GNU libtool
which installed GNU libtool? you mean the libtool that the project built for itself?
one is calling /opt/local/bin/glibtool, the other is using apr's libtool (/opt/local/share/apr-1/build/libtool).
I don't know what "one" or "the other" is.
That's silly - I listed the 2 bugs, two builds, "one" and "the other". But now you're saying there
are three libtools involved -- the one in /opt/local/bin/glibtool, the one in /opt/local/share/apr-1/build/libtool, and the one in ${worksrcdir}/libtool?
I have the libtool port installed and do not see the problem. Maybe I would see the problem if I removed the libtool port?
From the looks of things MacPorts at some point changed the default setting for CC?
If that is the case, it means that people who had built e.g. apr before it was changed, and then tried to build apache after the change will see this breakage. Peter -- Peter O'Gorman http://pogma.com