building cross compiler fails for target powerpc-linux-gnuspe

building cross compiler fails for target powerpc-linux-gnuspe

[Németh Márton]

Hi,

I'm trying to build a gcc cross compiler for target powerpc-linux-gnuspe.
The binutils bulds without any problem but I'm not sure why building gcc
fails.

There is a description at http://gcc.gnu.org/install/download.html :
> If you also intend to build binutils (either to upgrade an existing
> installation or for use in place of the corresponding tools of your OS),
> unpack the binutils distribution either in the same directory or a
> separate one. In the latter case, add symbolic links to any components
> of the binutils you intend to build alongside the compiler (bfd, binutils,
> gas, gprof, ld, opcodes, ...) to the directory containing the GCC sources.

Let's take an example: I downloaded binutils-2.20.tar.bz2 and
gcc-core-4.4.2.tar.bz2. Then I did:

$ tar xjvRf gcc-core-4.4.2.tar.bz2
$ cd gcc-4.4.2
$ tar xjvRf ../binutils-2.20.tar.bz2
$ ln -s binutils-2.20 binutils
$ cd ..
$ mkdir gcc-build
$ cd gcc-build
$ ../gcc-4.4.2/configure --target=powerpc-linux-gnuspe --prefix=/home/nmarci/usr/local/gcc --disable-shared --disable-threads --enable-languages=c
$ make

When executing this procedure the build fails with:

checking for powerpc-linux-gnuspe-gcc... /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/bin/
-B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/include -isystem
/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include
checking for suffix of object files... configure: error: in `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
make[1]: Leaving directory `/usr/src/gcc-build'
make: *** [all] Error 2

In the file powerpc-linux-gnuspe/libgcc/config.log I can find the following
messages:

configure:2393: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -V </dev/null >&5
xgcc: '-V' must come at the start of the command line
configure:2396: $? = 1
configure:2415: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -o conftest -g -O2     c
onftest.c  >&5
/usr/src/gcc-build/./gcc/as: line 76: exec: : not found
configure:2418: $? = 1
configure:2590: checking for suffix of object files
configure:2611: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -c -g -O2    conftest.c
>&5
/usr/src/gcc-build/./gcc/as: line 76: exec: : not found
configure:2614: $? = 1

It seems that the script gcc/as tries to execute an empty string. In gcc/as I can
see that ORIGINAL_AS_FOR_TARGET="".

So what's wrong with the procedure?

Regards,

	Márton Németh

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Németh Márton]

Németh Márton wrote:
> Hi,
> 
> I'm trying to build a gcc cross compiler for target powerpc-linux-gnuspe.
> The binutils bulds without any problem but I'm not sure why building gcc
> fails.
> 
> There is a description at http://gcc.gnu.org/install/download.html :
>> If you also intend to build binutils (either to upgrade an existing
>> installation or for use in place of the corresponding tools of your OS),
>> unpack the binutils distribution either in the same directory or a
>> separate one. In the latter case, add symbolic links to any components
>> of the binutils you intend to build alongside the compiler (bfd, binutils,
>> gas, gprof, ld, opcodes, ...) to the directory containing the GCC sources.
> 
> Let's take an example: I downloaded binutils-2.20.tar.bz2 and
> gcc-core-4.4.2.tar.bz2. Then I did:
> 
> $ tar xjvRf gcc-core-4.4.2.tar.bz2
> $ cd gcc-4.4.2
> $ tar xjvRf ../binutils-2.20.tar.bz2
> $ ln -s binutils-2.20 binutils
> $ cd ..
> $ mkdir gcc-build
> $ cd gcc-build
> $ ../gcc-4.4.2/configure --target=powerpc-linux-gnuspe --prefix=/home/nmarci/usr/local/gcc --disable-shared --disable-threads --enable-languages=c
> $ make
> 
> When executing this procedure the build fails with:
> 
> checking for powerpc-linux-gnuspe-gcc... /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/bin/
> -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/include -isystem
> /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include
> checking for suffix of object files... configure: error: in `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
> make[1]: *** [configure-target-libgcc] Error 1
> make[1]: Leaving directory `/usr/src/gcc-build'
> make: *** [all] Error 2
> 
> In the file powerpc-linux-gnuspe/libgcc/config.log I can find the following
> messages:
> 
> configure:2393: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
> ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
> linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -V </dev/null >&5
> xgcc: '-V' must come at the start of the command line
> configure:2396: $? = 1
> configure:2415: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
> ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
> linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -o conftest -g -O2     c
> onftest.c  >&5
> /usr/src/gcc-build/./gcc/as: line 76: exec: : not found
> configure:2418: $? = 1
> configure:2590: checking for suffix of object files
> configure:2611: /usr/src/gcc-build/./gcc/xgcc -B/usr/src/gcc-build/./gcc/ -B/home/nmarci/usr/local/gcc/powerpc-lin
> ux-gnuspe/bin/ -B/home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/lib/ -isystem /home/nmarci/usr/local/gcc/powerpc-
> linux-gnuspe/include -isystem /home/nmarci/usr/local/gcc/powerpc-linux-gnuspe/sys-include -c -g -O2    conftest.c
>> &5
> /usr/src/gcc-build/./gcc/as: line 76: exec: : not found
> configure:2614: $? = 1
> 
> It seems that the script gcc/as tries to execute an empty string. In gcc/as I can
> see that ORIGINAL_AS_FOR_TARGET="".
> 
> So what's wrong with the procedure?

I tried in a different way:

$ tar xjvRf binutils-2.20.tar.bz2
$ mkdir binutils-build
$ cd binutils-build
$ ../binutils-2.20/configure --target=powerpc-linux-gnuspe --prefix=/home/nmarci/usr/local/binutils
$ make
$ make install
$ cd ..
$ export PATH=$PATH:/home/nmarci/usr/local/binutils/bin
$ tar xjvRf gcc-core-4.4.2.tar.bz2
$ mkdir gcc-build
$ cd gcc-build
$ ../gcc-4.4.2/configure --target=powerpc-linux-gnuspe --prefix=/home/nmarci/usr/local/gcc --disable-shared --disable-threads --enable-languages=c
$ make

Now the build fails again, but at a different point. The build fails because different header files
are not found, like string.h, stdio.h, stdint.h.

What is the step which is missing? Or have I missed to disable building libgcc?


../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:33:43: error: string.h: Nincs ilyen fájl vagy könyvtár
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:34:54: error: stdio.h: Nincs ilyen fájl vagy könyvtár
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:54,
                 from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:36:
../../../../gcc-4.4.2/libgcc/gstdint.h:6:20: error: stdint.h: Nincs ilyen fájl vagy könyvtár
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:36:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:56:50: error: signal.h: Nincs ilyen fájl vagy könyvtár
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:36:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:79: error: expected specifier-qualifier-list before ‘int32_t’
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:36:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:237: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:238: error: expected declaration specifiers or ‘...’ before ‘int32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:240: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextGetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:241: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:241: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:242: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextSaveStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:244: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:247: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:249: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextTestSavedStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.h:250: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextTestStatus’
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:37:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:40:50: error: stdlib.h: Nincs ilyen fájl vagy könyvtár
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:37:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:95: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decSTICKYTAB’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:96: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decPOWERS’
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:37:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:99: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decDPD2BIN’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:100: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decBIN2DPD’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:101: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decDPD2BINK’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:102: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decDPD2BINM’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:103: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decDPD2BCD8’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:104: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decBIN2BCD8’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:105: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decBCD2DPD’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:225: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘d2utable’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:286: error: expected specifier-qualifier-list before ‘uint8_t’
In file included from ../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:37:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:325: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decCOMBMSD’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decNumberLocal.h:326: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decCOMBFROM’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:49: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decSTICKYTAB’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:54: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decPOWERS’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:67: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextClearStatus’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:68: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:68: error: ‘mask’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:68: error: (Each undeclared identifier is reported only once
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:68: error: for each function it appears in.)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:85: error: expected declaration specifiers or ‘...’ before ‘int32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextDefault’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:87: error: ‘decContext’ has no member named ‘digits’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:88: error: ‘decContext’ has no member named ‘emax’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:89: error: ‘decContext’ has no member named ‘emin’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:90: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:91: error: ‘decContext’ has no member named ‘traps’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:92: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:93: error: ‘decContext’ has no member named ‘clamp’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:97: error: ‘kind’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:102: error: ‘decContext’ has no member named ‘digits’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:103: error: ‘decContext’ has no member named ‘emax’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:104: error: ‘decContext’ has no member named ‘emin’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:105: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:106: error: ‘decContext’ has no member named ‘traps’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:107: error: ‘decContext’ has no member named ‘clamp’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:113: error: ‘decContext’ has no member named ‘digits’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:114: error: ‘decContext’ has no member named ‘emax’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:115: error: ‘decContext’ has no member named ‘emin’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:116: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:117: error: ‘decContext’ has no member named ‘traps’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:118: error: ‘decContext’ has no member named ‘clamp’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:124: error: ‘decContext’ has no member named ‘digits’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:125: error: ‘decContext’ has no member named ‘emax’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:126: error: ‘decContext’ has no member named ‘emin’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:127: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:128: error: ‘decContext’ has no member named ‘traps’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:129: error: ‘decContext’ has no member named ‘clamp’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:137: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextGetRounding’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:160: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:171: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextGetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:188: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:188: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextRestoreStatus’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:189: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:189: error: ‘mask’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:190: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:190: error: ‘newstatus’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:204: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextSaveStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextSetRounding’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:219: error: ‘decContext’ has no member named ‘round’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:233: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextSetStatus’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:234: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:234: error: ‘status’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:235: error: ‘decContext’ has no member named ‘traps’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:235: warning: implicit declaration of function ‘raise’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:235: error: ‘SIGFPE’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextSetStatusFromString’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:254: warning: implicit declaration of function ‘strcmp’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:255: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:257: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:259: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:261: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:263: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:265: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:267: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:269: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:275: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:277: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:279: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:281: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:283: error: too many arguments to function ‘__decContextSetStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:286: error: ‘NULL’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextSetStatusFromStringQuiet’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:306: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:308: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:310: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:312: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:314: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:316: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:318: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:320: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:326: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:328: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:330: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:332: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:334: error: too many arguments to function ‘__decContextSetStatusQuiet’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:337: error: ‘NULL’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:349: error: expected declaration specifiers or ‘...’ before ‘uint32_t’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextSetStatusQuiet’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:350: error: ‘decContext’ has no member named ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:350: error: ‘status’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextStatusToString’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:362: error: ‘int32_t’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:362: error: expected ‘;’ before ‘status’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:366: error: ‘status’ undeclared (first use in this function)
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:361: warning: unused parameter ‘context’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: At top level:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:397: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextTestSavedStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:411: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or ‘__attribute__’ before ‘__decContextTestStatus’
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c: In function ‘__decContextZeroStatus’:
../../../../gcc-4.4.2/libgcc/../libdecnumber/decContext.c:424: error: ‘decContext’ has no member named ‘status’
make[4]: *** [decContext.o] Error 1
make[4]: Leaving directory `/usr/src/gcc-build/powerpc-linux-gnuspe/nof/libgcc'
make[3]: *** [multi-do] Error 1
make[3]: Leaving directory `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc'
make[2]: *** [all-multi] Error 2
make[2]: Leaving directory `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc'
make[1]: *** [all-target-libgcc] Error 2
make[1]: Leaving directory `/usr/src/gcc-build'
make: *** [all] Error 2

Regards,

	Márton Németh

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Kai Ruottu]

Németh Márton wrote:
> Hi,
>
> I'm trying to build a gcc cross compiler for target powerpc-linux-gnuspe.
> The binutils bulds without any problem but I'm not sure why building gcc
> fails.
>   
On the contrary your GCC build succeeded !  How else you could have 
'xgcc', 'cc1', 'collect2' etc.
which are just the GCC parts?
> $ ../gcc-4.4.2/configure --target=powerpc-linux-gnuspe --prefix=/home/nmarci/usr/local/gcc --disable-shared --disable-threads --enable-languages=c
> $ make
>   

The 'make' means 'make all', the default "GCC build" doesn't mean the 
same as 'make all-gcc' !
> checking for suffix of object files... configure: error: in `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc':
>   

The 'libgcc' is the GCC helper library built for the $target USING the 
"ready-to-run" new GCC.
So you have your new GCC ready and can use it to compile all kind of 
things like a Linux kernel
and here the 'libgcc' library!
> So what's wrong with the procedure?
>   

You seemingly didn't read my earlier reply where I told : "and then  
configuring GCC and making
& installing it using 'make all-gcc ; make install-gcc',  should 
work..."  What was unclearly said in
this?

Compiling and linking things with a target compiler requires headers and 
libraries for this target,
in this case for Linux/PPC, the "native" headers (in '/usr/include') and 
libraries (in '/lib' and '/usr/lib')
are for the native,  Linux/x86 or Linux/x86_64 assumed,  target. and 
therefore not 'suitable'.

If you really want to produce libraries and applications for 
'powerpc-linux-gnuspe', then you must
have a proper glibc made for that!  Producing GCC then expects this 
existing already.  But for
just the SPE-variation there probably aren't any freely downloadable 
glibcs. But for the generic
Linux/PPC there are many like the Fedora/PPC and OpenSuSE/PPC distros. 
One could build
a complete "GCC" with 'libgcc', 'libstdc++' etc. with one of them as the 
"bootstrap" glibc.  But
after that you must produce a proper glibc for Linux/PPC-SPE with the 
new "complete" GCC.
This already has its 'libgcc' etc. libs made for the $target, 
'powerpc-linux-gnuspe' but the base
glibc is for the generic 'powerpc-linux-gnu'...  Quite surely the 
generic code in the bootstrap
glibc would work in a SPE CPU but not being very "optimal"....

You told that you will need ONLY a "kernel compiler", and making this 
has already succeeded!
Just write :

   make install-gcc

and see whether it will succeed!    Producing a "complete compiler"  
with a C library is then
much more complicated issue as you could see from the previous :(
 


> Regards,
>
> 	Márton Németh
>
>   

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Kai Ruottu]

Kai Ruottu wrote:
> Németh Márton wrote:
>> Hi,
>>
>> I'm trying to build a gcc cross compiler for target 
>> powerpc-linux-gnuspe.
>> The binutils bulds without any problem but I'm not sure why building gcc
>> fails.
>>   
> On the contrary your GCC build succeeded !  How else you could have 
> 'xgcc', 'cc1', 'collect2' etc.
> which are just the GCC parts?
>> $ ../gcc-4.4.2/configure --target=powerpc-linux-gnuspe 
>> --prefix=/home/nmarci/usr/local/gcc --disable-shared 
>> --disable-threads --enable-languages=c
>> $ make
>>   
>
> The 'make' means 'make all', the default "GCC build" doesn't mean the 
> same as 'make all-gcc' !
>> checking for suffix of object files... configure: error: in 
>> `/usr/src/gcc-build/powerpc-linux-gnuspe/libgcc':
>>   
>
> The 'libgcc' is the GCC helper library built for the $target USING the 
> "ready-to-run" new GCC.
> So you have your new GCC ready and can use it to compile all kind of 
> things like a Linux kernel
> and here the 'libgcc' library!

Unclearly told...  The right words would have been: "can TRY TO use it 
to compile all kind of things
like a Linux kernel and here the 'libgcc' library".   It has taken years 
since I last compiled a Linux
kernel but I assume it not requiring a 'libgcc' for the target system.  
Producing 'libgcc' however needs
the standard C headers for the target Linux system....   The 
'include/asm*' and 'include/linux', the
"kernel headers", should be enough when producing a Linux kernel, it is 
assumed (by me) to not
require anything from 'libgcc' like "soft-float" routines for a CPU 
without a FPU...

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Kai Ruottu]

Kai Ruottu wrote:
> Unclearly told...  The right words would have been: "can TRY TO use it 
> to compile all kind of things
> like a Linux kernel and here the 'libgcc' library".   It has taken 
> years since I last compiled a Linux
> kernel but I assume it not requiring a 'libgcc' for the target 
> system.  Producing 'libgcc' however needs
> the standard C headers for the target Linux system....   The 
> 'include/asm*' and 'include/linux', the
> "kernel headers", should be enough when producing a Linux kernel, it 
> is assumed (by me) to not
> require anything from 'libgcc' like "soft-float" routines for a CPU 
> without a FPU...
Again, when one must guess, googling helps, with search words "libgcc 
required in kernel compile"
the first hit was :

http://lkml.indiana.edu/hypermail/linux/kernel/0711.1/0937.html

Generally I myself wouldn't use my time to these "should it or should it 
not work" etc. issues but
simply provide something which surely should work, in your case that 
"complete GCC" with
some (temporary) glibc, be it then only for a generic  Linux/PPC and no  
optimal support for
the SPE CPUs.

So:

Adding the '--with-sysroot=$sysroot', where $sysroot is your own choice 
for the suitable
place for the target C library ('glibc'),  into your binutils and GCC 
configures.  And then
unpacking the main 'glibc-*.ppc.rpm' and the 'glibc-devel-*.ppc.rpm'  or 
some '.deb'
equivalents  into it :

     $sysroot/lib
     $sysroot/usr/include
     $sysroot/usr/lib

would be a good start in the "build a complete GCC" project.  Later when 
needing the
optimal 'powerpc-linux-gnuspe' glibc, building it from glibc sources and 
installing it into
the same $sysroot would come in question.  It would then be ready to be 
copied into
the root filesystem on the target platform, the runtimes from it....

Another route when one doesn't want to learn how to build binutils, GCC 
and glibc
separately, one at a time, is to try those "scripts for dummies", the 
"crosstool*" ones.
AFAIK they will always start from absolute scratch and don't teach 
anything about
how one builds these components one at a time, when needing to fix or 
update one
of the components....

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Hector Oron]

Hi,

2010/1/22 Kai Ruottu <kai.ruottu@wippies.com>:
> Adding the '--with-sysroot=$sysroot', where $sysroot is your own choice for
> the suitable
> place for the target C library ('glibc'),  into your binutils and GCC
> configures.  And then
> unpacking the main 'glibc-*.ppc.rpm' and the 'glibc-devel-*.ppc.rpm'  or
> some '.deb'
> equivalents  into it :
>
>    $sysroot/lib
>    $sysroot/usr/include
>    $sysroot/usr/lib

  Excuse me, but I was just about to post about this, but using
*non-standard paths* in the sysroot. Is it posible to change/add paths
to default sysroot paths, if I would like to do that (as default for
my compiler) should i patch the source or is there any option suitable
for my case?



-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."

Re: building cross compiler fails for target powerpc-linux-gnuspe

[Hector Oron]

Hi again,

2010/1/23 Hector Oron <hector.oron@gmail.com>:
>  Excuse me, but I was just about to post about this, but using
> *non-standard paths* in the sysroot. Is it posible to change/add paths
> to default sysroot paths, if I would like to do that (as default for
> my compiler) should i patch the source or is there any option suitable
> for my case?

Sorry, I just realized that could be done overloading -isystem with
*=*. I just need to test it. If you think this is wrong or you have an
alternative the question remains.

Thanks
-- 
 Héctor Orón

"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."