I cross compile software for a system where I can't use shared libraries using gentoo. Therefor it would be useeful, if --disable-static would only be passed to configure in the giflib ebuild, if the static-libs use flag is not present. Reproducible: Always
Created attachment 276687 [details, diff] proposed patch A patch for the current giflib ebuild adding the static-libs use flag
ugh, it seems static libs were wrongly punted Thomas: you cannot indiscriminately disable static libraries. you must always build both, or add a USE=static-libs flag. especially without revbumping.
Hmm static-libs useflag added. I thought none would really need such thing as static libs on imaging library. (not even other distros provide static lib for this one, and they really provide a lot of them) @Florian: you don't need to cc yourself on your own bugs as reporter gets the mails anyway :)
other distros doing it wrong doesnt mean we should. all library packages should be providing static libs (or USE=static-libs). the latest change isnt quite right yet ... you cant delete .la files when static libs are installed.
Mike, you *can* delete .la files when installing static libraries that have no further dependencies than libc (which is the case with giflib): http://blog.flameeyes.eu/2009/09/28/removing-la-files-for-dum-w-uncertain-people
except for the part where giflib links against a lot of other libs based on its USE flags
Good point, revbumped.
