Jakub Jelinek wrote:
On Fri, Feb 20, 2009 at 11:29:48AM +0100, Ralf Corsepius wrote:
Jakub Jelinek wrote:
On Fri, Feb 20, 2009 at 09:55:27AM +0100, Ralf Corsepius wrote:
Except of very few rare exceptional cases you don't have to know it.
And when, you can always manually add --build to these package's specs.
There are plenty of packages that care, usually to pick up optimized
assembly for various CPUs, or whether it is possible to use atomic
instructions or not.
s/--build/--host/
Would you mind to list them?
I don't have time to search for them right now, so just a few:
gcc (e.g. libstdc++-v3, libgomp, etc. in it)
glibc
gmp
openssl
Then fix them.
You are trying to make small differences in configure triplets irrelevant,
Because they are irrelvant. The relevance is inside of the CFLAGS.
but in reality sparc-linux is something different from sparcv9-linux
from say sparcv9v-linux
1. neither sparc-linux nor sparc9c-linux are part of Fedora.
2. sparc/sparcv9-sun-* is _the_ classic example of a multilib'ed
environment, using a multilib'ed toolchain.
GCC and friend had been able to support them 10 years ago.
and i586-linux is different from i386-linux.
No. Same toolchain, different CFLAGS, different multilibs.
If you omit --host and --build, config.guess will guess these from the
build box and then you'll wonder why packages built on say SPARC Niagara
don't work at all on older sparc64 boxes, eventhough the packages are still
sparcv9.rpm and similarly in the i?86 world.
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
