Summary: | x11-libs/cairo - .la files are removed from install causing build failures in reverse dependency packages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jiří Moravec <qjim> |
Component: | [OLD] Development | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | jmbsvicetto |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jiří Moravec
2011-02-16 20:05:37 UTC
Those files aren't needed. 1. Portage had been cleaning up installed la files for awhile, so references to other la files are replaced with references to the libs 2. There's always revdep-rebuild/lafilefixer (In reply to comment #1) > Those files aren't needed. > > 1. Portage had been cleaning up installed la files for awhile, > so references to other la files are replaced with references to the libs > 2. There's always revdep-rebuild/lafilefixer > Sorry but I'm not so sure. I have no inconsistencies which can be finded and resolved by revdep-rebuild. lafilefixer, if I understand correctly its function, is a tool for correcting corrupted existing .la files and not for creating new ones. And I actually tried this tool before bug filling: 'lafilefixer --justfixit /usr/lib64/'. My problem is that I'm unable to upgrade or reemerge some sw installed on my pc, so from my point of view those files ARE needed. So how I can resolve that problem? Or better: How you resolved that problem? That's cause it doesn't create any, just fixes existing ones. IIRC, 'lafilefixer --justfixit' doesn't take other arguments. What was it's output ? Also, how old is your gentoolkit ? (In reply to comment #3) > That's cause it doesn't create any, just fixes existing ones. > > IIRC, 'lafilefixer --justfixit' doesn't take other arguments. > What was it's output ? > > Also, how old is your gentoolkit ? > app-portage/gentoolkit-0.3.0_rc11-r3. Does it mean that I need devel-9999 version? lafilefixer --justfixit has 824 lines and all of them ended with "already clean, skipping update." (In reply to comment #4) > (In reply to comment #3) > > That's cause it doesn't create any, just fixes existing ones. > > > > IIRC, 'lafilefixer --justfixit' doesn't take other arguments. > > What was it's output ? > > > > Also, how old is your gentoolkit ? > > > > app-portage/gentoolkit-0.3.0_rc11-r3. Does it mean that I need devel-9999 > version? > > lafilefixer --justfixit has 824 lines and all of them ended with "already > clean, skipping update." > Apparently everything is functional. After I runned 'lafilefixer --justfixit' emerging both cairo and libgksu were without problem. So I'm sorry about this alarm. Is there, just for case when another user will experience same situation, any howto or warning about this portage/build behaviour? Which I probable missed? (In reply to comment #5) > Is there, just for case when another user will experience same situation, any > howto or warning about this portage/build behaviour? Which I probable missed? Newer portage versions, like the one you are using, already fix this, but for packages installed before you upgraded sys-apps/portage, the way to go is to run lafilefixer and all your installed packages should be OK for the future. |