From: Michael Smith <msmith@cbnco.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Gnu/stubs-32.h not found
Date: Tue, 12 Jan 2010 10:19:03 -0500 [thread overview]
Message-ID: <4B4C92E7.3090107@cbnco.com> (raw)
In-Reply-To: <1263305804.3675.396.camel@mill.internal.reciva.com>
Phil Blundell wrote:
> On Tue, 2010-01-12 at 13:32 +0300, Perepelica Alexander wrote:
> Ah, I see. So, you were right: it is in fact a multilibs problem. What
> has happened here is that gcc is trying to build a 32-bit version of
> libgcc2, but you haven't compiled a 32-bit version of glibc yet.
>
> There are two possible fixes:
>
> - write a variant .bb file to build a 32 bit glibc, and arrange for
> gcc-cross to DEPEND on that; or
>
> - patch t-linux64, and/or the gcc configury, to stop it trying to build
> the 32-bit multilib.
One hack that worked for me is to amend the gcc-cross recipe to include:
# glibc only built the 64-bit stubs, so don't try to build a 32-bit gcc
EXTRA_OECONF_append_x86_64 = " --disable-multilib"
And for gcc-cross-intermediate:
do_compile_prepend() {
# On x86_64, glibc-initial stages crti.o to
# x86_64-oe-linux/lib64/crti.o.
# When gcc-cross-intermediate tries to build libgcc, it looks
# for x86_64-oe-linux/lib/../lib64/crti.o.
# Create the "lib" dir so this shenanigan works.
install -d ${STAGING_DIR_TARGET}/lib
}
Mike
next prev parent reply other threads:[~2010-01-12 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 7:49 Gnu/stubs-32.h not found Perepelica Alexander
2010-01-12 9:36 ` Phil Blundell
2010-01-12 10:27 ` Perepelica Alexander
2010-01-12 10:32 ` Perepelica Alexander
2010-01-12 14:16 ` Phil Blundell
2010-01-12 15:19 ` Michael Smith [this message]
2010-01-12 15:26 ` Perepelica Alexander
[not found] ` <578649919.1263312754.64087816.75695@mcgi68.rambler.ru>
2010-01-12 16:26 ` Perepelica Alexander
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=4B4C92E7.3090107@cbnco.com \
--to=msmith@cbnco.com \
--cc=openembedded-devel@lists.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.