On 09/11/2010 02:13 AM, Stéphane Guedon wrote:
synce few days, I have a message of portage suggestiung me to use the "static-
libs" USE flag for media-libs/jpeg-6b.
What may be the consequence ? Please be gentle with explaining this sorte of
things, as I have not the knowledges to understand the full compile process,
otherwise I am a little bit familiar with it !
I have jpeg-8b, so I can't be sure about 6b. I just turned on the static-libs
USE flag and re-installed jpeg. The only difference is that the 'static' lib
"/usr/lib/libjpeg.a" wasn't there before and it is now, that's all.
Is your system trying to upgrade jpeg to a newer version? I notice that 6b
doesn't use any USE flags, and the newer versions do use the static-libs flag.
(Just re-installing 6b shouldn't complain about USE flags because the package
doesn't look for them.)
Any program that uses the dynamic libjpeg.so would need to be re-compiled if
the version of jpeg changes. If the static library is used instead, the
program no longer needs libjpeg.so because the static library is linked into
the binary executable at compile-time. The price you pay is a larger binary
executable, but you never need to worry about future jpeg version changes.
I don't know how portage chooses between static and dynamic libs while building
a package. Anyone else know?
