This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: building for mips target glibc-headers target


From: "Arno Schuring" <aelschuring@hotmail.com>
To: "Daniel Laird" <danieljlaird@hotmail.com>,<dank@kegel.com>
CC: <crossgcc@sources.redhat.com>
Subject: Re: building for mips target glibc-headers target
Date: Tue, 12 Apr 2005 11:06:01 +0200



So if i understand this properly.

I can patch my crosstool with the sanitized headers patch
I can then download this and save it somewhere so get&patch does not get it
I should then run corsstool as usual with the SANITIZED_LINUX_DIR variable set

LINUX_SANITIZED_HEADER_DIR :)


Other than that, you are correct. (remark #2 is a matter of choice, though. getandpatch should be able to download it)

I should still let the install-glibc-headers section in the crosstool.sh run

Glibc-headers and kernel-headers are complementary, so yes you should leave it in. However there is a parallel discussion going on here about whether we need that separate glibc-headers step. Apparently in some cases it is possible to build a core-gcc without the glibc-headers.


when it finishes I should have a toolchain with the following
binutils 2.15.96
glibc 2.3.4
gcc 3.4.3

I can then use this toolchain to build a 2.6.11.6 kernel for my target

Short answer: yes
Long answer:
Any 2.6.x kernel really. If you would have used gcc-3.3.x you could also have built a linux-2.4.x kernel with the same toolchain. Building the kernel is not the greatest issue. But (and please someone correct me if I'm wrong) the programs you compile with this toolchain will not run under a 2.4 kernel. The libc version and kernel headers version mainly affect on what system(s) your programs will run, not what you can or cannot compile with it.


Arno


np: Dream Theater - The Great Debate


I have tried this. I still get an error When it tries to build-glibc-headers i get the following
gcc -mabi=32 -march=mips32 -mtune=r4600 -D_MIPS_SZPTR=32 -D_MIPS_SIM=1 -E -dM -MD -MP -MF /home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers/bits/stdio_lim.dT -MT '/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers/bits/stdio_lim.h /home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers/bits/stdio_lim.d' \
-Iinclude -I. -I/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers -Ilibio -I/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers -Isysdeps/mips/elf -Isysdeps/unix/sysv/linux/mips/mips32 -Isysdeps/unix/sysv/linux/mips -Isysdeps/unix/sysv/linux -Isysdeps/gnu -Isysdeps/unix/common -Isysdeps/unix/mman -Isysdeps/unix/inet -Isysdeps/unix/sysv -Isysdeps/unix/mips/mips32 -Isysdeps/unix/mips -Isysdeps/unix -Isysdeps/posix -Isysdeps/mips/mips32 -Isysdeps/mips -Isysdeps/ieee754/flt-32 -Isysdeps/ieee754/dbl-64 -Isysdeps/wordsize-32 -Isysdeps/mips/fpu -Isysdeps/ieee754 -Isysdeps/generic/elf -Isysdeps/generic -nostdinc -isystem /usr/lib/gcc/i386-redhat-linux/3.4.2/include -isystem /opt/nxlinux/gcc/gcc-3.4.3-glibc-2.3.4/mipsel-linux-gnu/include -xc - -o /home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers/bits/stdio_lim.hT
cc1: error: invalid option `abi=32'
:0: error: bad value (mips32) for -march= switch
:0: error: bad value (r4600) for -mtune= switch
make[2]: *** [/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers/bits/stdio_lim.st] Error 1
make[2]: Leaving directory `/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/glibc-2.3.4'
make[1]: *** [sysdeps/gnu/errlist.c] Error 2
make[1]: Leaving directory `/home/laird/ccm_wa/ipstb/ipstb_laird/ipstb/build/packages/crosstool-0.30_cbics/build/mipsel-linux-gnu/gcc-3.4.3-glibc-2.3.4/build-glibc-headers'
make: *** [crosstool.make] Error 2
I can see that it has picked up these flags from sysdeps/mips/mips32/Makefile.


I can patch these out which is what other people seem to be doing but should i do this?

Cheers
Dan



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]