mod_* & libtool

Ryan Schmidt ryandesign at
Sun Jun 3 15:33:54 PDT 2012

On Jun 3, 2012, at 11:05, Bjarne D Mathiesen wrote:

> Bradley Giesbrecht wrote:
>> On Jun 3, 2012, at 7:36 AM, Bjarne D Mathiesen wrote:
>>> I'm in the process of re-writing the active and/or working mod_* ports
>>> for the new Debian/Ubunto layout.
>>> However, I've run into a problem with most of them :-(
>>> They are all installing perfectly under the present Apache layout.
>>> I've compared the logs from a perfect install & a failed install.
>>> What goes wrong is the following :
>>> /macportstest/share/apr-1/build/libtool --silent --mode=link --tag=CC
>>> /usr/bin/clang -o  -rpath  -module -avoid-version
>>> mod_chroot.lo
>>> the -rpath is empty on a failed build.
>>> As far as I can see, -rpath ought to be the dir where the module is
>>> going to be installed , but setting :
>>> 	--libexecdir=[dict get ${apache} libexecdir] \
>> FYI, the tcl (8.4.7) supplied with Leopard (Mac OS X 10.5) does not appear to have "dict".
>> Perhaps we can use an array so we don't leave Leopard behind unnecessarily?
> hmmm ... macports has 8.5.11
> can we fix it so that macports uses it's own tcl after installation ???

No, we cannot. MacPorts has to be able to function well enough to install its first port when there aren't any ports installed yet. That precludes core functionality of MacPorts from using MacPorts Tcl.

> I've used /dict/ extesively in Apache2, & it's uploaded to your
> bitbucket so you've got the opportunity to test it under 10.5 on a
> build-bot :-) I don't ahve an active 10.5 at present :-(

We only have a 10.6 and 10.7 buildbot; there are no plans to create buildbots for earlier OS versions.

More information about the macports-dev mailing list