Re: "arm-linux-gnueabi-gcc-4.4 -march=armv4t" silently produces "armv7"
W dniu 08.11.2011 09:42, Steffen Dettmer pisze:
> I installed 6.0.1 (according to /etc/debian_version) on an ARM board
> with v5TE architecture which is not able to execute armv7 code.
> Precompiled binaries are v4T. Now I tried to install gcc toolchain to
> build my application.
> I tried to compile with "arm-linux-gnueabi-gcc-4.4 -march=armv4t", but
> I do not get "Tag_CPU_arch: v4T" (readelf -A) but "Tag_CPU_arch: v7".
> It seems that the tool chain was built incorrectly and specific to
> armv7
> I considered to rebuilt the packages
> (gcc-4.4-arm-linux-gnueabi_4.4.5-15ubuntu1_i386.deb, others)
> tech info:
>
> $ arm-linux-gnueabi-gcc-4.4 -mcpu=arm9tdmi -march=armv4t -msoft-float
> -mfloat-abi=soft -mthumb-interwork -v -O0 -Wall -o hello-arm hello.c
> Using built-in specs.
> Target: arm-linux-gnueabi
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro
> 4.4.5-15ubuntu1'
> --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
> --program-suffix=-4.4 --enable-shared --enable-multiarch
> --with-multiarch-defaults=i386-linux-gnu --enable-linker-build-id
> --with-system-zlib --libexecdir=/usr/lib --without-included-gettext
> --enable-threads=posix
> --with-gxx-include-dir=/usr/arm-linux-gnueabi/include/c++/4.4.5
> --libdir=/usr/lib --enable-nls --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-objc-gc --disable-sjlj-exceptions
> --with-arch=armv7-a --with-float=softfp --with-fpu=vfpv3-d16
> --with-mode=thumb --disable-werror --enable-checking=release
> --program-prefix=arm-linux-gnueabi-
> --includedir=/usr/arm-linux-gnueabi/include --build=i686-linux-gnu
> --host=i686-linux-gnu --target=arm-linux-gnueabi
> --with-headers=/usr/arm-linux-gnueabi/include
> --with-libs=/usr/arm-linux-gnueabi/lib
Please do not install Ubuntu cross toolchain in Debian systems. It is
armv7a by default and will not change. You should install toolchain from
Emdebian.org repository instead.
Reply to: