Skip to contentSkip to conversation

Kernel Cross Compiling

DISCUSSION Stephen M. Kenton 4 participants 4 messages Feb 14, 2004 – Feb 15, 2004

lore
Share & tools
lore
#0 lore raw

The problems with GCC cross builds are known and are targeted for GCC 3.5 since the changes will apparently be invasive. If you have not seen it yet, Dan Kegel has a very nice package called crosstool with lots of comments about the contortions of cross compiling.
http://kegel.com/crosstool

smk

#1 lore raw
Quoted 6 lines · Stephen M. Kenton

The problems with GCC cross builds are known and are targeted for GCC 3.5 since the changes will apparently be invasive. If you have not seen it yet, Dan Kegel has a very nice package called crosstool with lots of comments about the contortions of cross compiling.
http://kegel.com/crosstool

thanks for the info, I read/tested that one too, some time ago, but decided against this approach, as it builds the glibc, which I do not need for the kernel toolchain at all and I didn't want to bother with another source that won't compile on arch xy ... maybe the wrong decision? I don't know ...

best,
Herbert

Quoted 6 lines

smk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#2 lore raw

Herbert,

Quoted 8 lines · Herbert Poetzl
Quoted 1 line

http://kegel.com/crosstool

thanks for the info, I read/tested that one too, some time ago, but decided against this approach, as it builds the glibc, which I do not need for the kernel toolchain at all and I didn't want to bother with another source that won't compile on arch xy ... maybe the wrong decision? I don't know ...

you might also want to have a look at the idea behind PTXdist (see
http://www.pengutronix.de/software/ptxdist_en.html) which is also able to build toolchains and do all the necessary tweaking, without building a glibc (just only run 'make xchain-gccstage1' to get a compiler without glibc). It follows the same approach for the patch repositories like Dan and we are syncing heavily.

The whole toolchain building is a huge mess at the moment.

Robert

Signature · 5 lines
 Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry
   Handelsregister:  Amtsgericht Hildesheim, HRA 2686
     Hornemannstraße 12,  31137 Hildesheim, Germany
    Phone: +49-5121-28619-0 |  Fax: +49-5121-28619-4
#3 lore raw
Quoted 6 lines · Herbert Poetzl
Quoted 6 lines

thanks for the info, I read/tested that one too, some time ago, but decided against this approach, as it builds the glibc, which I do not need for the kernel toolchain at all and I didn't want to bother with another source that won't compile on arch xy ... maybe the wrong decision? I don't know ...

Quoted 7 lines · Robert Schwebel

you might also want to have a look at the idea behind PTXdist (see
http://www.pengutronix.de/software/ptxdist_en.html) which is also able to build toolchains and do all the necessary tweaking, without building a glibc (just only run 'make xchain-gccstage1' to get a compiler without glibc). It follows the same approach for the patch repositories like Dan and we are syncing heavily.
The whole toolchain building is a huge mess at the moment.

(a) The idiot thing was screwed wrt. binutils when the things were prefixed with e.g. sparc64-linux-gnu-$PROG; I managed to decipher where the paths were and just patch in the names of the crossutils.
(b) The stuff produced broken kernels; I had to resort to native builds anyway (which far from ideal, since it target violates host/target separation), and lost money getting a second of its kind to repair that state of affairs.

-- wli