Am 16.04.2010 16:08, schrieb Sylvestre Ledru:
By the way, in all cases, the best optimization will be to build custom
packages of atlas. By design, prebuilt packages of Atlas are not the
best solution.
The same is also true for the ffmpeg (and mplayer) package, which I
co-maintain. However, a valid conclusion from this insight may be that
it does not make too much sense to provide such fine-grained optimized
prebuilt libraries, but stay with a reasonable generic set that is
known to "make a difference".
The previous mechanism was to play with LD_LIBRARY_PATH. I consider this
solution a strong improvement for "lambda user".
Indeed!
I can provide you a compromise here.
Beside the current packages, I can try to do a package called
libatlas3gf-all
which will contain all the various optimisation. The ld stuff would be
done in this package.
Well, this will add another package to the current list of alternative
dependencies for libblas3gf, which is IMHO too long already and a
reason why I filed this bug report in the first place.
How are you going to do the "ld stuff" ni this package? Will you add
symlinks from e.g. from /usr/lib/atlas-sse2 to /usr/lib/sse2?
Beside the refactoring and the new upstream release, what I did was to
replace the "LD_LIBRARY_PATH way" by update-alternatives.
Understood now, thanks. ;)
- Fabian
PS: BTW, is it possible that the directory structure that I just
suggested was already present in the Lenny versions of the packages?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
