Bug 289899 – dev-util/lafilefixer removal request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Philip Hazel 2009-10-20 19:02:24 UTC]

As requested in bug 275597, I am opening a new report and will attach data. Having installed libogg 1.1.4, and run lafilefixer, epiphany will no longer build because of the lack of libogg.la. I will create an attachment of the lafilefixer output and the build log - looks like I have to create this bug first though.

[Comment 1 Philip Hazel 2009-10-20 19:03:15 UTC]

Created attachment 207715 [details]
Output from lafilefixer

[Comment 2 Philip Hazel 2009-10-20 19:04:42 UTC]

Created attachment 207716 [details]
build log for epiphany

[Comment 3 Rafał Mużyło 2009-10-20 19:13:18 UTC]

Most probably the last la file is broken in a way,
that makes lafilefixer abort before it does its job.
I'm not sure, what's in that file, but perhaps
removing '/' from that place will be enough.

[Comment 4 Philip Hazel 2009-10-20 19:18:06 UTC]

But there is NO .la file present. The upgrade to libogg removed it.

[Comment 5 Lars Wendler (Polynomial-C) (RETIRED) 2009-10-20 19:25:23 UTC]

*** This bug has been marked as a duplicate of bug 218286 ***

[Comment 6 Diego Elio Pettenò (RETIRED) 2009-10-20 19:27:54 UTC]

Not a duplicate, you found something lafilefixer chokes on:

/usr/lib/kde3/libwpimport.la

[Comment 7 Diego Elio Pettenò (RETIRED) 2009-10-20 19:28:51 UTC]

attach that .la file please… and check from which package it comes from. I smell a problem similar to bug #276460.

[Comment 8 Lars Wendler (Polynomial-C) (RETIRED) 2009-10-20 19:29:16 UTC]

Oops, sorry, maybe I was a bit too fast on duplicating this bug. I apologize for that...

[Comment 9 Philip Hazel 2009-10-21 14:56:09 UTC]

Created attachment 207832 [details]
Old .la file that breaks lafilefixer

[Comment 10 Philip Hazel 2009-10-21 14:57:04 UTC]

(In reply to comment #7)
> attach that .la file please… and check from which package it comes from. I
> smell a problem similar to bug #276460.

That was the clue that solved this for me ... when I checked on that file, it did not belong to any package, and it was dated Feb 2007. So I renamed it out of the way and ran lafilefixer again. It promptly found another similar file. And so on; there were 23 files in all, all apparently related to KDE and ImageMagick. Once I had got rid of them all, lafilefixer ran without comment, and then I was able to build epiphany. I will attach the file that caused the original problem, as this perhaps should be recognized by lafilefixer.

Also, if lafilefixer had given a clearer error message I might have recognized that there was a problem. As it is, it is not clear that this output indicates that there is a problem: 

Debug information:
/usr/lib/kde3/libwpimport.la
/-lstdc++
Holy Moley, Dorothy, we ain't in Kansas and Luke, I'm not your father

First time I saw that I ignored it as just an output comment.

[Comment 11 Peter Alfredsen (RETIRED) 2009-10-22 19:07:22 UTC]

(In reply to comment #10)

> Also, if lafilefixer had given a clearer error message I might have recognized
> that there was a problem. As it is, it is not clear that this output indicates
> that there is a problem: 

To be honest, I didn't expect that debug message trigger, if the file wasn't corrupt somehow, in which case I would like to know about it. I should probably make it non-fatal or 'repair' the /-lstdc++ bit. For now, you can just remove the slash from /-lstdc++ and lafilefixer should go on its merry way. Next release will have a fix.

[Comment 12 Fox 2009-11-23 23:46:15 UTC]

I also get:

Debug information:
/usr/lib/kde3/libkspreadcalc.la
/-lstdc++
Holy Moley, Dorothy, we ain't in Kansas and Luke, I'm not your father

(trying to get libogg.la magically appear (libogg 1.1.4 is installed, but lafilefixer does not seem to summon it from the depths of la-hell)).

[Comment 13 SpanKY 2011-11-27 00:03:01 UTC]

*** Bug 304557 has been marked as a duplicate of this bug. ***

[Comment 14 Pacho Ramos 2012-03-09 08:38:32 UTC]

(In reply to comment #11)
> (In reply to comment #10)
> 
> > Also, if lafilefixer had given a clearer error message I might have recognized
> > that there was a problem. As it is, it is not clear that this output indicates
> > that there is a problem: 
> 
> To be honest, I didn't expect that debug message trigger, if the file wasn't
> corrupt somehow, in which case I would like to know about it. I should
> probably make it non-fatal or 'repair' the /-lstdc++ bit. For now, you can
> just remove the slash from /-lstdc++ and lafilefixer should go on its merry
> way. Next release will have a fix.

Peter, do you have that fix somewhere we could get it and apply to our ebuilds? Thanks

[Comment 15 Pacho Ramos 2013-06-04 20:30:04 UTC]

I am not sure if we still need this: I am not running it for months, portage already fixes .la files and paludis people don't like this. Maybe it's time to treeclean

[Comment 16 Samuli Suominen (RETIRED) 2013-06-04 20:58:02 UTC]

I'd claim this is no longer useful due to the massive cleanups done in gentoo-x86/

[Comment 17 Sergey Popov 2013-06-06 09:05:50 UTC]

# Sergey Popov <[e-mail]> (06 Jun 2013)
# Abandoned package, most of functions incorporated in portage
# Masked for removal in 30 days, bug #289899
dev-util/lafilefixer

[Comment 18 Sergey Popov 2013-07-12 00:16:53 UTC]

lafilefixer was dropped from tree