On 10/29/2010 01:11 AM, Paolo Bonzini wrote: > On 10/28/2010 04:59 PM, Markus Duft wrote: >> thinking of gnulib, i can see a lot of potential problems, starting fex, >> that gnulib >> modules are copied into the packages, rather than gnulib beeing an installed >> library >> that is linked against (is this true always?). > > It is true that gnulib is usually copied into packages. However, it is > possible to put multiple gnulib modules into a single statically linked > library. This is what gentoo does with its ebuild; you can search recent > archives for "libposix", too (which is just a selection of gnulib modules > improving the POSIX-ness of a system).
mhm, so at least ATM, it's most of the time static. would it be much of a problem to build things both shared and static? also, is there a chance i'm able to install libc.a and libc.so in a way that i never destroy anything on any system? is it wanted for gnulib at all to install such scripts? > >> in gentoo prefix (gentoo main too? idk) there is a "gnulib" ebuild, which >> builds a >> library of gnulib to fix some system deficiencies, but IIRC it's static >> only. i'd >> rather like suacomp to be static wherever possible to ease bugfixing, >> upgrades, etc. > > There's something inconsistent here. :) hah, lol - of course, suacomp should be shared wherever possible ;) > > Paolo > >
