* After emerging the (beta) update of x11-libs/cairo, some dependent packages failed to build due to missing libcairo.la file. * The ebuild /usr/portage/x11-libs/cairo/cairo-1.10.0-r1.ebuild compile actually created that file, though the install stage missed it, and so the qmerge does of course. * I worked around by manually copying libcairo.la to /usr/lib64 and running lafilefixer /usr/lib64/libcairo.la Reproducible: Always Steps to Reproduce:
> * I worked around by manually copying libcairo.la to /usr/lib64 and running > lafilefixer /usr/lib64/libcairo.la I should also say, that if libtool and friends weren't so greek to me, I might have found a smarter fix, or the major cause of this problem. Needing lafilefixer seems a bug to me too.
Please read metadata.xml before randomly assigning bugs.
And the .la file is specifically removed by the ebuild. Not closing until we decide what to do about this.
(In reply to comment #3) > And the .la file is specifically removed by the ebuild. Not closing until we > decide what to do about this. > Just change use static-libs || find "${D}" -type f -name '*.la' -exec rm -f '{}' \; to find "${D}" -type f -name '*.la' -exec rm -f '{}' + and be done with it, no .la files are required even for static-libs because cairo comes with a pkg-config file. they're entirely pointless. perhaps add a elog message telling users to run lafilefixer at most
*** Bug 336695 has been marked as a duplicate of this bug. ***
fixed in 1.10.0-r3 by keeping .la files around for now.
What is wrong with just having to run lafilefixer? Installing the .la file just increases the risk of carrying useless dependencies around. (and in case of cairo, dependencies that might change over time) Now that we have --as-needed it's not that harmful, but still useless.
(In reply to comment #7) > What is wrong with just having to run lafilefixer? Because cairo isn't a small library that's only used by 2 other apps. It's a major lib used by gtk and countless other libs/apps. Dropping the .la file for only cairo is like saying "Fuck You!" to more than half of our desktop users. Don't worry, we hate .la files just as much as anybody else and we *will* remove them. But we'll do it in coordination with other teams, with proper communication and planning. Cheers
