Re: checking sysdep dirs... configure: error: The arm is not supported

[Hua Li <privatestuffs at gmail dot com>]

Dear Carlos,

It is not a problem related to GCC, I think. Because even if I added
GCC to bashrc or bash_profile, there is still the same error.

[point@digital build]$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc-4.6.2/libexec/gcc/i686-pc-linux-gnu/4.6.2/lto-wrapper
Target: i686-pc-linux-gnu
Configured with: ./configure --prefix=/usr/local/gcc-4.6.2
--enable-threads=posix --disable-checking --disable-multilib
--enable-language=c,c++ --with-gmp=/usr/local/gmp-5.0.4
--with-mpfr=/usr/local/mpfr-3.1.0 --with-mpc=/usr/local/mpc-0.9
Thread model: posix
gcc version 4.6.2 (GCC)

[point@digital build]$ gcc --version
gcc (GCC) 4.6.2
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Attached is the full text of config.log, and I couldn't see any way to
solve this problem.

Thanks again.

On 3/5/12, Carlos O'Donell <carlos@systemhalted.org> wrote:
> On Sat, Mar 3, 2012 at 10:45 PM, Hua Li <privatestuffs@gmail.com> wrote:
>> Thanks, Carlos.
>>
>> I got glibc-ports, and then configured again, there appeared a new
>> error about GCC:
>>
>> [point@digital build]$ CC=arm-linux-gcc AR=arm-linux-ar
>> RANLIB=arm-linux-ranlib ../glibc-2.14/configure --host=arm-linux
>> --prefix=/home/point/armtools/arm-linux --enable-add-ons=nptl,ports
>> --with-header=/home/point/armtools/arm-linux/include
>> --with-gcc=/usr/local/gcc-4.6.2
>>
>> checking for makeinfo... no
>> checking for sed... sed
>> checking version of sed... 4.2.1, ok
>> checking for autoconf... autoconf
>> checking whether autoconf works... yes
>> configure: error:
>> *** These critical programs are missing or too old: gcc
>> *** Check the INSTALL file for required versions.
>>
>> What's wrong with GCC ?
>
> Look at config.log to see what configure was attempting to do before it
> failed.
>
> That will give you a hint.
>
> For example I don't think your --wigh-gcc option is valid.
>
> Generally you add your new gcc bin path to the front of the PATH env var.
>
> Alternatively you specify it directly in CC e.g. export
> CC=/path/to/gcc; export CXX=/path/to/g++
>
> Hopefully that helps.
>
> Cheers,
> Carlos.
>

Attachment: config.log
Description: Binary data