Re: An old question:gcc and arm-linux-gcc?



uusky wrote:

Thank you very much!!

When I read the manual of the GNU assembler as, and I find that gas
has option of
"
[ -m[arm]1 | -m[arm]2 | -m[arm]250 | -m[arm]3 | -m[arm]6 | -m[arm]7[t]
[[d]m[i]] ]
[ -m[arm]v2 | -m[arm]v2a | -m[arm]v3 | -m[arm]v3m | -m[arm]v4 | -m[arm]
v4t ]
"
and
"
-m68000 | -m68008 | -m68010 | -m68020 | -m68030 | -m68040 | -m68060
| -m68302 | -m68331 | -m68332 | -m68333 | -m68340 | -mcpu32 | -m5200
"
, and so on. That is my question!

Its the same with gas. All parts of your toolchain are built for one
architecture.

For example here I'm using different toolchains for various targets:

$ ls arm-v5-toolchain
arm-v5te-linux-gnueabi-addr2line arm-v5te-linux-gnueabi-gccbug
arm-v5te-linux-gnueabi-ranlib arm-v5te-linux-gnueabi-ar
arm-v5te-linux-gnueabi-gcov arm-v5te-linux-gnueabi-readelf
arm-v5te-linux-gnueabi-as arm-v5te-linux-gnueabi-gdb
arm-v5te-linux-gnueabi-run arm-v5te-linux-gnueabi-c++
arm-v5te-linux-gnueabi-gdbtui arm-v5te-linux-gnueabi-size
arm-v5te-linux-gnueabi-c++filt arm-v5te-linux-gnueabi-gprof
arm-v5te-linux-gnueabi-strings arm-v5te-linux-gnueabi-cpp
arm-v5te-linux-gnueabi-ld arm-v5te-linux-gnueabi-strip
arm-v5te-linux-gnueabi-g++ arm-v5te-linux-gnueabi-nm
arm-v5te-linux-gnueabi-gcc arm-v5te-linux-gnueabi-objcopy
arm-v5te-linux-gnueabi-gcc-4.3.2 arm-v5te-linux-gnueabi-objdump

$ ls arm-v6-toolchain
arm-1136jfs-linux-gnueabi-addr2line arm-1136jfs-linux-gnueabi-gprof
arm-1136jfs-linux-gnueabi-ar arm-1136jfs-linux-gnueabi-ld
arm-1136jfs-linux-gnueabi-as arm-1136jfs-linux-gnueabi-nm
arm-1136jfs-linux-gnueabi-c++ arm-1136jfs-linux-gnueabi-objcopy
arm-1136jfs-linux-gnueabi-c++filt arm-1136jfs-linux-gnueabi-objdump
arm-1136jfs-linux-gnueabi-cpp arm-1136jfs-linux-gnueabi-ranlib
arm-1136jfs-linux-gnueabi-g++ arm-1136jfs-linux-gnueabi-readelf
arm-1136jfs-linux-gnueabi-gcc arm-1136jfs-linux-gnueabi-run
arm-1136jfs-linux-gnueabi-gcc-4.3.2 arm-1136jfs-linux-gnueabi-size
arm-1136jfs-linux-gnueabi-gccbug arm-1136jfs-linux-gnueabi-strings
arm-1136jfs-linux-gnueabi-gcov arm-1136jfs-linux-gnueabi-strip
arm-1136jfs-linux-gnueabi-gdb arm-1136jfs-linux-gnueabi-gdbtui

$ ls powerpc
powerpc-603e-linux-gnu-addr2line powerpc-603e-linux-gnu-gcc-4.3.2
powerpc-603e-linux-gnu-objdump powerpc-603e-linux-gnu-ar
powerpc-603e-linux-gnu-gccbug powerpc-603e-linux-gnu-ranlib
powerpc-603e-linux-gnu-as powerpc-603e-linux-gnu-gcov
powerpc-603e-linux-gnu-readelf powerpc-603e-linux-gnu-c++
powerpc-603e-linux-gnu-gdb powerpc-603e-linux-gnu-run
powerpc-603e-linux-gnu-c++filt powerpc-603e-linux-gnu-gdbtui
powerpc-603e-linux-gnu-size powerpc-603e-linux-gnu-cpp
powerpc-603e-linux-gnu-gprof powerpc-603e-linux-gnu-strings
powerpc-603e-linux-gnu-embedspu powerpc-603e-linux-gnu-ld
powerpc-603e-linux-gnu-strip powerpc-603e-linux-gnu-g++
powerpc-603e-linux-gnu-nm powerpc-603e-linux-gnu-gcc
powerpc-603e-linux-gnu-objcopy

(and so on for x86...)

It makes sense to name the toolchain in this way. The autotools are using
parts of the names to guess for what kind of architecture a program should
be built.

jbe
.