Review Re-Request: ATLAS, a fast implementation of BLAS and LAPACK
qspencer at ieee.org
Thu Sep 15 20:02:24 UTC 2005
Dominik 'Rathann' Mierzejewski wrote:
>On Wednesday, 14 September 2005 at 00:18, Quentin Spencer wrote:
>>>Not quite so. You can put all x86 RPMs in one repo and yum will select
>>>automatically the one matching your arch from them. Example:
>>>In an i386 repo, there are:
>>>You have, let's say, an Athlon CPU.
>>>yum install atlas-devel
>>>will select atlas-devel-0.1-1.athlon.rpm for installation.
>>>That said, x86_64 (and PPC, of course) *are* different and cannot be put
>>>in the same repo.
>>On the other hand, can the FE build system do that?
>That I don't know, I've only just started playing with it on my
>buildboxes. But I think it can, considering that we have kernel.i586,
>kernel.i686 and kernel.athlon all built from the same src.rpm.
>>How to I write the spec file to handle all of that
>>correctly? Are there any example I can look at?
>kernel is one, glibc is another and openssl is yet another.
I'll look into this, but I might point out that all of the examples you
have given are in Core, which doesn't use the same build system (though
I understand that could change eventually). My understanding of the
Extras buildsys is that it just does the three base archs and there
isn't (yet) a way to so subarchitectures such as i686, pentium4, etc.
For a previous discussion on how to package all of this, see:
I might add that the approach I'm using here is exactly what Debian is
doing, which is the only other effort I'm aware of to package this for
More information about the fedora-extras-list