RE: Problem building gcc-3.4.1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Well, since no one has responded i will answer my own question.

Theer are two problems with gcc configuration:
1. --without-headers option is broken so badly that I did not even bother to fix it. Instead I ahve built gclib headers and used them with --with-headers and --disable-shared option to compiler.

2. Solution to header problem uncovered another problem. GCC configuration does not handle --with-newlib option properly. If --with-newlib is used, 'inhibit-libc' should be defined no matter what (at least I understand it this way). Instead, it also makes check for usage of --with-headers option. If --with-headers is used, inhibit_libc is undefined, reagrdless of -with-newlib. At the moment I did a quick hack to always define inhibit-libc when --with-newlib is used.

This allowed me to build a bootstrap compiler. I will try to build libraries and then fully blown compiler. I will let all know if there any more problems.

Rudolf

-----Original Message-----
From: gcc-help-owner@xxxxxxxxxxx [mailto:gcc-help-owner@xxxxxxxxxxx]On
Behalf Of Rudolf Ladyzhenskii
Sent: Friday, July 23, 2004 2:35 PM
To: gcc-help@xxxxxxxxxxx
Subject: Problem building gcc-3.4.1


Hi, all

I am trying to build a cross-compiler toolchain.
Host is i68, target (for now) is i386.

host compiler is GCC 3.2.2

I have built binutils, now I am building the compiler.
configure --target=i386-linux --prefix=/home/shared/tools --without-headers --with-newlib --enable-languages=c

when making gcc, I am getting an error:

---------------
mkdir -p -- libgcc
if [ -f stmp-dirs ]; then true; else touch stmp-dirs; fi
/home/rudolfl/project/ibis/build-tools/gcc-3.4.1/gcc/xgcc -B/home/rudolfl/projec
t/ibis/build-tools/gcc-3.4.1/gcc/ -B/home/shared/tools/i386-linux/bin/ -B/home/s
hared/tools/i386-linux/lib/ -isystem /home/shared/tools/i386-linux/include -isys
tem /home/shared/tools/i386-linux/sys-include -O2  -DIN_GCC -DCROSS_COMPILE   -W
 -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-defi
nition  -isystem ./include  -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FL
OAT_NOT_NEEDED -Dinhibit_libc -I. -I. -I. -I./. -I./../include   -DL_muldi3 -c .
/libgcc2.c -o libgcc/./_muldi3.o
In file included from ./tm.h:11,
                 from ./libgcc2.c:43:
./config/i386/linux.h:217:20: signal.h: No such file or directory
./config/i386/linux.h:218:26: sys/ucontext.h: No such file or directory
make[2]: *** [libgcc/./_muldi3.o] Error 1
make[2]: Leaving directory `/home/rudolfl/project/ibis/build-tools/gcc-3.4.1/gcc
'
make[1]: *** [libgcc.a] Error 2
make[1]: Leaving directory `/home/rudolfl/project/ibis/build-tools/gcc-3.4.1/gcc
'
make: *** [all-gcc] Error 2
---------------------------------------------

Relevant headers were copied into /home/shared/i386-linux/include Header files were copied from kernel 2.6.7. In particular headers from include/linux, include/asm-i386 and include/asm-generic were copied.

signal.h is present in /home/shared/tools/i386-linux/include/linux, but thsi directory is not included in the compiler include path.

Is it a bug or I am doing something wrong?

Thanks,

/*******************************************************/
Rudolf Ladyzhenskii
Senior Design Engineer
Open Networks Pty. Ltd.
Level 26, 35 Collins Street,
Melbourne VIC 3000
e-mail: rudolfl.ladyzhenskii@xxxxxxxxxx
phone: +61 3 9656 5107
fax:     +61 3 9656 5122
web: www.opennw.com
/*******************************************************/




[Index of Archives]     [Linux C Programming]     [Linux Kernel]     [eCos]     [Fedora Development]     [Fedora Announce]     [Autoconf]     [The DWARVES Debugging Tools]     [Yosemite Campsites]     [Yosemite News]     [Linux GCC]

  Powered by Linux