On Freitag 16 Oktober 2009, walt wrote: > On 10/16/2009 04:37 AM, Neil Bothwick wrote: > > On Fri, 16 Oct 2009 12:20:30 +0100, Peter Humphrey wrote: > >> I thought I'd have a play with swami, but the emerge fails with > >> "/bin/sed: can't read /usr/lib64/libogg.la: No such file or directory", > >> and indeed there is none such. > > > > The elog message from the last libogg install explains this. Run > > lafilefixer --justfixit. > > There is no manpage for lafilefixer, but the --help flag prints: > > --justfixit Choose some reasonable dirs, such as /usr/lib*, > etc. , find all .la files and fix them to not use .la files for linking > > I can't make sense out of that -- one of the major uses of libtool (I > thought) is for linking. Can anyone 'splain that to me? > > Thanks. >
AFAIK the help printout is not entirely correct. It corrects the path' used in the la files, I recommend this reads: http://blog.flameeyes.eu/2008/04/14/what-about-those-la-files http://blog.flameeyes.eu/2008/07/02/again-about-la-files-or-why-should-they-be- killed-off-sooner-rather-than-later http://blog.flameeyes.eu/2009/04/18/some-details-about-our-old-friends-the-la- files http://blog.flameeyes.eu/2009/09/28/removing-la-files-for-dum-w-uncertain-people
