An emerge of glib does not produce *.la files in /usr/lib .. We need *.la files to emerge gtk+ Reproducible: Always Steps to Reproduce: 1.emerge glib 2. 3. Actual Results: produces the *.a and *.so* libs but not the *.la lib Expected Results: I need the *.la lib Need *.la libs to emerge gtk+
I can't find the relevant bug at the moment, but those la files are removed on purpose (and they're definitely *not* needed) - see the old ChangeLog entry (09 Feb 2011).
--*definitely*-- is a big word. I did an emerge of glib prior to an emerge of gtk+, but the gtk+ emerge would fail with the message of unable to locate a *.la file. IIRC there are four *.la files required. I could not emerge gtk+ unless: (1) I had to do a manual download of glib, ./configure and make in a work directory I call /home/downloads (2) copy four *.la files to /usr/lib. Sorry, but I do not remember which *.la files they were except they were the four that in the glib tree library subdirectories that were soft-linked to the previous directory. (3) run emerge gtk+ ...and everything emerged just fine. And that's *definitely* what happened.
"I do not remember which *.la files they were" translates pretty much to WORKSFORME. "copy four *.la files to /usr/lib", while not equal to "I've broken my system", still mean that you have files in the system that aren't covered by portage, so many of your future bugs will become your very own. *definitely* is the correct word here, just search http://blog.flameeyes.eu/ for entries about libtool.
