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] |
For the kernel ABI. Eventually a special set of kernel ABI headers could be used instead.
I am sorry I did not get it. Would appreciate helping me understand more on this.
(Why that particular set of snapshots? Why not gcc-3.4.0-glibc-2.3.2?)
I had first used gcc-3.4.0-glibc-2.3.2.dat from crosstool-0.28-rc31.tar. But since I had problem compiling the kernel with the created toolchain, I was planning to use the crosstools from the "current" link.
What problem are you seeing?
I have detailed the problem before. Before that following are the steps I did to generate the toolchain (apologize it is long):
1. Made a copy of armv5b-softfloat.dat named it as xscale.dat and changed TARGET to TARGET=armv5l-softfloat-linux
2. Made a copy of demo-armv5b-softfloat.sh, named it as demo-xscale.sh. Changed eval to eval `cat xscale.dat gcc-3.4.0-glibc-2.3.2.dat` sh all.sh --notest
Note: I just noticed that gcc-3.4.0-glibc-2.2.5.dat and gcc-3.4.0-glibc-2.1.3.dat has by default 2.4.21 kernel. May be I should not have used glibc-2.3.2 and hence the problems I am seeing compling 2.4.21 kernel with gcc 3.4.0.
3. Modified gcc-3.4.0-glibc-2.3.2.dat's LINUX_DIR to LINUX_DIR=linux-2.4.21
4. execute "sh demo-xscale.sh". The toolchain creation was successfull.
5. I have a customized (support for new xscale hardware) 2.4.21 kernel source code. This source code has no problem with gcc 3.2. I set the path to the toolchain's bin directory and compiled. I had three major problems during compile time and did he following changes:
c. include/asm/unistd.h:397: warning: conflicting types for built-in function '_exit'. So I commented out this _exit() function.
After these changes, Compilition of the kernel went fine. However during linking to generate vmlinux, there were several "relocation truncated to fit: R_ARM_PC24" errors.
My previous thread "pthread.h not found - error while generating toolchain for xscale" details the errors.
Should I have let crosstools not download linux code from kernel.org and instead modify it to use the kernel code I have ?
Thanks Bill
From: Dan Kegel <dank@kegel.com>
To: Bill Garner <bill__garner@hotmail.com>
CC: linux-arm-toolchain@lists.arm.linux.org.uk, crossgcc <crossgcc@sources.redhat.com>
Subject: Re: Questions on crosstool
Date: Sat, 07 Aug 2004 21:26:34 -0700
Bill Garner wrote:Would appreciate if I can know:
1. For TARGET= option for e.g. arm-softfloat-linux-gnu, while generating the toolchain will the substring "softfloat", "linux" and "gnu" be used to generate specific toolschains? Know that substring "arm" is used. Can I have the option e.g. TARGET=arm-foo ?.
No, you can't have arm-foo. Various tools really do expect a target of form chip-mfr-linux-gnu. arm-linux is a common value for target, but a couple (annoying) tools (mostly the testsuite) don't like that abbreviation, and insist on arm-something-linux-gnu. I used to wish I could use a shorter target, but I now accept that the long target name is needed.
2. Why Linux source code is required (through LINUX_DIR=) to generate the toolchain ?
For the kernel ABI. Eventually a special set of kernel ABI headers could be used instead.
3. Has anybody successfuly compiled 2.4.2x arm kernel with toolchain created using gcc-3.4-2003xxxx-glibc-2.3.2.dat file(s).
(Why that particular set of snapshots? Why not gcc-3.4.0-glibc-2.3.2?)
What problem are you seeing? - Dan
--
My technical stuff: http://kegel.com
My politics: see http://www.misleader.org for examples of why I'm for regime change
------ 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] |