GCC installation problem using crosstool

GCC installation problem using crosstool

[Aprev]

When using Crosstool to setup GCC for ARM (running on x86 linux) I get the
following error at the end of the installation:

/temp/crosstool-0.43/build/arm-unknown-linux-gnu/gcc-4.1.0-glibc-2.2.2/binutils-2.16.1/configure
--target=arm-unknown-linux-gnu --host=i686-host_pc-linux-gnulibc1
--prefix=/opt/crosstool/gcc-4.1.0-glibc-2.2.2/arm-unknown-linux-gnu
--disable-nls
--with-sysroot=/opt/crosstool/gcc-4.1.0-glibc-2.2.2/arm-unknown-linux-gnu/arm-unknown-linux-gnu
creating cache ./config.cache
checking host system type... i686-host_pc-linux-gnulibc1
checking target system type... arm-unknown-linux-gnu
checking build system type... i686-host_pc-linux-gnulibc1
checking for a BSD compatible install... /usr/bin/install -c
checking whether ln works... yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... no
configure: error: installation or configuration problem: C compiler cannot
create executables.

---

The complete log and sh-file is attached to the document. I'm rather new to
Linux and am not sure how to interpret the log.

http://www.nabble.com/file/p13249711/log.txt log.txt 
http://www.nabble.com/file/p13249711/demo-arm.sh demo-arm.sh 

BR


-- 
View this message in context: http://www.nabble.com/GCC-installation-problem-using-crosstool-tf4639064.html#a13249711
Sent from the gcc - Help mailing list archive at Nabble.com.

Re: GCC installation problem using crosstool

[Andrew Haley]

Aprev writes:
 > 
 > When using Crosstool to setup GCC for ARM (running on x86 linux) I get the
 > following error at the end of the installation:
 > 
 > /temp/crosstool-0.43/build/arm-unknown-linux-gnu/gcc-4.1.0-glibc-2.2.2/binutils-2.16.1/configure
 > --target=arm-unknown-linux-gnu --host=i686-host_pc-linux-gnulibc1
 > --prefix=/opt/crosstool/gcc-4.1.0-glibc-2.2.2/arm-unknown-linux-gnu
 > --disable-nls
 > --with-sysroot=/opt/crosstool/gcc-4.1.0-glibc-2.2.2/arm-unknown-linux-gnu/arm-unknown-linux-gnu
 > creating cache ./config.cache
 > checking host system type... i686-host_pc-linux-gnulibc1
 > checking target system type... arm-unknown-linux-gnu
 > checking build system type... i686-host_pc-linux-gnulibc1
 > checking for a BSD compatible install... /usr/bin/install -c
 > checking whether ln works... yes
 > checking whether ln -s works... yes
 > checking for gcc... gcc
 > checking whether the C compiler (gcc  ) works... no
 > configure: error: installation or configuration problem: C compiler cannot
 > create executables.
 > 
 > ---
 > 
 > The complete log and sh-file is attached to the document. I'm rather new to
 > Linux and am not sure how to interpret the log.
 > 
 > http://www.nabble.com/file/p13249711/log.txt log.txt 
 > http://www.nabble.com/file/p13249711/demo-arm.sh demo-arm.sh 

You don't have a working C compiler on your *host* system!

First, make sure you have gcc installed on your host system.  You OS
has some commands to install packages: on fedora it would be

  yum install gcc

Building a cross compiler is much harder than building a native
compiler.  If I were you I'd first try to build a native compiler from
the same sources, and only then try building for ARM.

Something like  

  <gcc srcdir>/configure
  make

just to make sure that gcc builds.  Once you've done that
successfully, leap into the magical world of crosstool.

Andrew.

Re: GCC installation problem using crosstool

[Aprev]

Thanks alot for the reply. I had gcc 4.1.2 installed, but something was
missing, apparently this command did the job:

sudo apt-get install gcc build-essential


So now the Crosstool-script went a little further before stopping again :(

I get a lot of warnings when running make, and then it stops on two errors.

please see attached log:  http://www.nabble.com/file/p13253738/log.txt
log.txt 


BR,
Andreas
-- 
View this message in context: http://www.nabble.com/GCC-installation-problem-using-crosstool-tf4639064.html#a13253738
Sent from the gcc - Help mailing list archive at Nabble.com.

Re: GCC installation problem using crosstool

[Aprev]

Seems the log was a bit truncated, here is the complete one:

http://www.nabble.com/file/p13254011/log.txt.zip log.txt.zip 
-- 
View this message in context: http://www.nabble.com/GCC-installation-problem-using-crosstool-tf4639064.html#a13254011
Sent from the gcc - Help mailing list archive at Nabble.com.

Re: GCC installation problem using crosstool

[Andrew Haley]

Aprev writes:
 > 
 > Seems the log was a bit truncated, here is the complete one:
 > 
 > http://www.nabble.com/file/p13254011/log.txt.zip log.txt.zip 

I don't see any error messages.

Andrew.

Re: GCC installation problem using crosstool

[Aprev]

Missing 2>&1, sorry.

http://www.nabble.com/file/p13269976/log2.txt.zip log2.txt.zip 



Andrew Haley-5 wrote:
> 
> Aprev writes:
>  > 
>  > Seems the log was a bit truncated, here is the complete one:
>  > 
>  > http://www.nabble.com/file/p13254011/log.txt.zip log.txt.zip 
> 
> I don't see any error messages.
> 
> Andrew.
> 
> 

-- 
View this message in context: http://www.nabble.com/GCC-installation-problem-using-crosstool-tf4639064.html#a13269976
Sent from the gcc - Help mailing list archive at Nabble.com.

Re: GCC installation problem using crosstool

[Andrew Haley]

Aprev writes:
 > 
 > Missing 2>&1, sorry.
 > 
 > http://www.nabble.com/file/p13269976/log2.txt.zip log2.txt.zip 

/home/andreas/temp/crosstool-0.43/build/arm-unknown-linux-gnu/gcc-4.1.0-glibc-2.2.2/gcc-2.95.3/gcc/config/arm/arm.c:286: warning: assignment discards qualifiers from pointer target type
/home/andreas/temp/crosstool-0.43/build/arm-unknown-linux-gnu/gcc-4.1.0-glibc-2.2.2/gcc-2.95.3/gcc/config/arm/arm.c:530: error: invalid lvalue in assignment
make[1]: *** [arm.o] Error 1

This is an lvalue cast:

arm.c:530:  arm_prog_mode = TARGET_APCS_32 ? PROG_MODE_PROG32 : PROG_MODE_PROG26;

arm.h:426:#define arm_prog_mode ((enum attr_prog_mode) arm_prgmode)
arm.md:47:(define_attr "prog_mode" "prog26,prog32" (const (symbol_ref "arm_prog_mode")))

That is a bug in gcc 2.95.  You need either to fix the bug or upgrade
to a more recent compiler.

A bug fix might be as simple as

arm.c:530:  arm_prgmode = TARGET_APCS_32 ? PROG_MODE_PROG32 : PROG_MODE_PROG26;

but it's still bad to be using such a very old compiler.

Andrew.