On Sat, Mar 10, 2007 at 09:33:14AM -0500, Laszlo (Laca) Peter wrote:

> The best way to fix .la files is deleting them.  Everything works
> fine without them, in fact things work better.
> 
> laca at ferrari:~> ls /usr/sfw/lib/lib*.la
> /usr/sfw/lib/libMagick++.la   /usr/sfw/lib/libgthread.la
> /usr/sfw/lib/libMagick.la     /usr/sfw/lib/libgtk.la
> /usr/sfw/lib/liba2ps.la       /usr/sfw/lib/libnetsnmp.la
> /usr/sfw/lib/libg2c.la        /usr/sfw/lib/libnetsnmpagent.la
> /usr/sfw/lib/libgdk.la        /usr/sfw/lib/libnetsnmphelpers.la
> /usr/sfw/lib/libgimpprint.la  /usr/sfw/lib/libnetsnmpmibs.la
> /usr/sfw/lib/libglib.la       /usr/sfw/lib/libstdc++.la
> /usr/sfw/lib/libgmodule.la    /usr/sfw/lib/libsupc++.la
> 
> All these should go.  Shall I file bugs?

Yes, please.  Nuking libtool shit puts a smile on my face.

And yes, we should enumerate all the *-config type scripts and
probably just rewrite them to return the things we know are right
instead of whatever the autobuild system thinks is right for the
arbitrary GNU/Linux system the author actually "tests" on.

-- 
Keith M Wesolowski              "Sir, we're surrounded!" 
FishWorks                       "Excellent; we can attack in any direction!" 

Reply via email to