From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC]: Toolchain build sequence alteration.
Date: Sat, 02 Aug 2008 14:03:08 +0200 [thread overview]
Message-ID: <g71idt$s09$1@ger.gmane.org> (raw)
In-Reply-To: <1216087105.10214.7.camel@isis>
Khem Raj wrote:
Currently we do
>
> cross-binutils -> kernel-headers -> uclibc-headers -> cross-gcc
> (--disable-shared) -> uclibc -> cross-gcc
>
> I think this can be improved and I implemented the following steps.
>
> cross-binutils -> cross-gcc (--disable-shared) -> kernel-headers ->
> eglibc/glibc/uclibc headers + startup files + dummy libc.so -> cross-gcc
> (--enable-shared) -> glibc/eglibc/uclibc -> cross-gcc
As we've noticed this breaks the iconv modules from glibc since they get
a NEEDED entry for /lib/libc.so (which in in libc6-dev) instead of
/lib/libc.so.6 (which in is libc6). You attempted to fix this with:
--- a/packages/gcc/gcc-cross-intermediate.inc
+++ b/packages/gcc/gcc-cross-intermediate.inc
@@ -16,6 +16,13 @@ EXTRA_OECONF = "--with-local-
+do_stage_prepend () {
+ # get rid of dummy libc.so
+ if [ -z "`file ${STAGING_DIR_TARGET}${layout_libdir}/libc.so | grep
"ASCII C program text"`" ]; then
+ rm -rf ${STAGING_DIR_TARGET}${layout_libdir}/libc.so
+ fi
+}
That breaks building a toolchain from scratch with "cannot find -lc"
during glibc-cross-intermediate staging. So I committed this:
--- a/packages/gcc/gcc-cross-intermediate.inc
+++ b/packages/gcc/gcc-cross-intermediate.inc
@@ -16,7 +16,7 @@ EXTRA_OECONF = "--with-local-
-do_stage_prepend () {
+do_stage_append () {
# get rid of dummy libc.so
This fixes builds from scratch for me (tried with armv5te and armv7a),
but I haven't tested if it breaks iconv again since I value working
builds over working iconv atm. I'm fairly sure it doesn't break iconv,
because the bogus libc.so is gone before glibc gets built, but as I
said, I haven't tested it.
regards,
Koen
next prev parent reply other threads:[~2008-08-02 12:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 1:58 [RFC]: Toolchain build sequence alteration Khem Raj
2008-07-15 7:34 ` Henning Heinold
2008-07-16 8:10 ` Khem Raj
2008-07-16 8:46 ` Koen Kooi
2008-07-16 15:27 ` Khem Raj
2008-07-16 20:43 ` Leon Woestenberg
2008-07-17 8:43 ` Khem Raj
2008-07-22 0:28 ` Khem Raj
[not found] ` <20080720014112.GA13759@oberlord>
2008-07-23 9:04 ` Khem Raj
2008-07-24 9:10 ` Richard Purdie
2008-07-24 16:05 ` Richard Purdie
2008-07-24 16:18 ` Koen Kooi
2008-07-25 7:33 ` Khem Raj
2008-07-25 10:01 ` Henning Heinold
2008-07-25 16:06 ` Khem Raj
2008-07-28 6:27 ` SH7760 Problems Stefano Regno
2008-08-02 12:03 ` Koen Kooi [this message]
2008-08-02 15:14 ` [RFC]: Toolchain build sequence alteration Phil Blundell
2008-08-02 15:45 ` Koen Kooi
2008-08-03 2:47 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='g71idt$s09$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.