This is the mail archive of the crossgcc@sourceware.org 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] |
Hi Yann, I try to make toolchain with following config: linux-2.6.20 glibc-2.5 gcc-4.1.1 little endian binutils-2.17.50.0.10 I run without problems till Installing binutils: done On the next step - installing C library headers, I get following error: Build failed in step "installing C library headers" Error Happened in "..ct-ng/scripts/build/libc_glibc.sh" at line # 13 called from "../ct-ng/scripts/buildToolchain.sh" at line # 118 called from "../ct-ng/scripts/crosstool.sh" at line # 247 I try to figure out - what could be the reason Regards, Jevgeni "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr> wrote in message 200702082245.32290.yann.morin.1998@anciens.enib.fr">news:200702082245.32290.yann.morin.1998@anciens.enib.fr... Hello all! About three months ago I wrote about the subject: cleaning up crosstool. It appeared to be a bigger task I thought it would. :-( So I stopped trying to think of a way to update crosstool, and tried a new approach: re-write it. You can check my work on my wiki: http://ymorin.is-a-geek.org/dokuwiki/doku.php?id=projects:crosstool And the code is available through anonymous svn access: svn co http://ymorin.is-a-geek.org/svn/crosstool/ct-ng The targeted audience are people with some good basis and the know-how about toolchains. Main features are: - menuconfig ( most important! :-) ), - design from the ground-up, - designed to support alternative components (see below), - kernel headers from headers_install with recent kernels, - large number of versions for gcc, glibc, uClibc, binutils and kernels, - some sample targets configurations, - a collection of patches vampirised from current crosstool and buildroot, plus a few by me, - improved (and eye-candy) logging facility, - documentation (sparse for now, improving), - ... My main concern was to be able to build toolchains with different components: - glibc or uClibc or ... - gcc or tcc or ... - linux or cygwin (or ?...) - etc... Hopefully adding one alternative component to the build process is as simple as adding a config file and a build script for this component (already there are glibc/uClibc). It's not fully ready yet, but I thought someone would like to have a look. Comments most welcome! Thank you for your attention. Regards, Yann E. MORIN. -- .-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ | | --==< °_° >==-- °------------.-------: X AGAINST | /e\ There is no | | http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. | °------------------------------°-------°------------------°--------------------° -- For unsubscribe information see http://sourceware.org/lists.html#faq -- For unsubscribe information see http://sourceware.org/lists.html#faq
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |