Le Mercredi 19 Mars 2003 18:31, Gwenole Beauchesne a �crit :
> On Wed, 19 Mar 2003, Guillaume Rousse wrote:
> > > No package will be built with MMX optimizations by default as there are
> > > Pentium out there without those extensions. However, if your
> > > application dynamically links against some optimized DSOs that would be
> > > fine to put those libraries in */lib/mmx/* or */lib/sse{,2}/*. But you
> > > will be stuck if they decided to dlopen() their plugins/libraries.
> >
> > An other option would be to have different packages for optimized and non
> > optimized libs/binaries, and use alternatives to use them transparently.
>
> The process described above doesn't need any alternatives. The glibc
> loader knows which library to load. e.g. say you have libfoo.so.1 in
> /usr/lib and one in /usr/lib/sse/. If your application has libfoo.so.1 as
> dependency, then glibc will load the */lib/sse/* one if your CPU supports
> SSE instructions.
That works only for libraries linked at compile time however, while symlinks
works also for binaries, and for dynamically loaded libraries.
Moreover, there are two different issues there: a packaging issue (should
optimisable package contains optimized code) and a system issue (how to
install this code to make it used).
--
Disks are always full. It is futile to try to get more disk space. Data
expands to fill any void.
-- Murphy's Computer Laws n�4
