On Feb 10, 2013, at 03:55, Jeremy Huddleston Sequoia wrote:
> On Feb 10, 2013, at 1:49 AM, Ryan Schmidt wrote:
>
>> I noticed pangox-compat doesn't link with icu even if I rebuild it now. Any
>> idea why it's immune? It does build with libtool. It's its own copy of GNU
>> libtool built at configure time, not MacPorts glibtool.
>
> The copy of glibtool it uses shouldn't matter. I don't know. Is
> pangox-compat not linking against harfbuzz?
Hmm, no, only with:
/opt/local/lib/libpangox-1.0.0.dylib (compatibility version 1.0.0,
current version 1.0.0)
/opt/local/lib/libpango-1.0.0.dylib (compatibility version 3201.0.0,
current version 3201.5.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current
version 169.3.0)
/opt/local/lib/libgobject-2.0.0.dylib (compatibility version 3401.0.0,
current version 3401.3.0)
/opt/local/lib/libgmodule-2.0.0.dylib (compatibility version 3401.0.0,
current version 3401.3.0)
/opt/local/lib/libglib-2.0.0.dylib (compatibility version 3401.0.0,
current version 3401.3.0)
/opt/local/lib/libintl.8.dylib (compatibility version 10.0.0, current
version 10.2.0)
/opt/local/lib/libX11.6.dylib (compatibility version 10.0.0, current
version 10.0.0)
>> There are still .la files in /usr/lib on Mountain Lion (in
>> /usr/lib/freeradius and /usr/lib/sasl2)
>
> ~ $ sw_vers
> ProductName: Mac OS X
> ProductVersion: 10.8.2
> BuildVersion: 12C60
>
> ~ $ ls /usr/lib/*la
> gls: cannot access /usr/lib/*la: No such file or directory
>
> I didn't see those ones in freeradius and sasl2 … time to file a radar =)
>
>> , and many in MacPorts in directories other than /opt/local/lib.
>
> Yeah, pretty much any port which builds a library with glibtool (which is the
> overwhelming majority of OSS libraries) will be in this boat.
>
>> Can we just go nuts and fs-traverse ${destroot} and remove all .la files
>> wherever they might be? We could use `file` to make sure they're text files
>> before doing so, in case some weird software somewhere uses its own .la
>> files that are not libtool files.
>
> I once got pissed at MacPorts and just nuked /opt/local/lib/*.la and nothing
> bad ever happened to me.
Given that you say .la files are not useful on OS X, and are evidently even
harmful, why does glibtool install them on OS X? Has this problem been brought
to the attention of the glibtool developers?
_______________________________________________
macports-dev mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-dev
