From: Jaap de Jong <jaap.dejong@nedap.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64
Date: Tue, 10 May 2011 17:04:59 +0200 [thread overview]
Message-ID: <4DC9541B.6070208@nedap.com> (raw)
In-Reply-To: <1305038299.8000.178.camel@phil-desktop>
On 05/10/2011 04:38 PM, Phil Blundell wrote:
> On Tue, 2011-05-10 at 14:57 +0200, Jaap de Jong wrote:
>> bitbake ends with
>> |
>> /media/OpenEmbedded/release-2010.12/tmp/sysroots/i686-linux/usr/x86_64/x86_64-angstrom-linux/bin/ld:
>> cannot find /lib64/libc.so.6 inside
>> /media/OpenEmbedded/release-2010.12/tmp/sysroots/x86_64-angstrom-linux
>>
>> There is only a lib directory and no lib64 directory...
> It seems that there is some disagreement between binutils and your C
> library about where the libs should be stored. Which DISTRO
> configuration are you using?
Build Configuration:
BB_VERSION = "1.8.18"
METADATA_BRANCH = "release-2010.12"
METADATA_REVISION = "dec3967"
TARGET_ARCH = "x86_64"
TARGET_OS = "linux"
MACHINE = "x86_64-generic"
DISTRO = "angstrom"
DISTRO_VERSION = "2010.12"
> If you make a symlink from lib -> lib64 inside the sysroot, does that
> allow the build to continue?
>
Tried that one...
|
/media/OpenEmbedded/release-2010.12/tmp/sysroots/i686-linux/usr/x86_64/x86_64-angstrom-linux/bin/ld:
cannot find /lib64/libc.so.6 inside
/media/OpenEmbedded/release-2010.12/tmp/sysroots/x86_64-angstrom-linux
so the answer is: no...
Jaap
next prev parent reply other threads:[~2011-05-10 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-10 8:13 x86_64 Jaap de Jong
2011-05-10 10:00 ` x86_64 Bernhard Reutner-Fischer
2011-05-10 10:04 ` x86_64 Eric Bénard
2011-05-10 10:06 ` x86_64 Phil Blundell
2011-05-10 11:02 ` x86_64 Jaap de Jong
2011-05-10 11:08 ` x86_64 Phil Blundell
2011-05-10 11:15 ` x86_64 Jaap de Jong
2011-05-10 12:57 ` x86_64 Jaap de Jong
2011-05-10 14:38 ` x86_64 Phil Blundell
2011-05-10 15:04 ` Jaap de Jong [this message]
2011-05-10 15:35 ` x86_64 Enrico Scholz
2011-05-10 15:47 ` x86_64 Michael Smith
2011-05-10 16:43 ` x86_64 Enrico Scholz
2011-05-10 16:15 ` x86_64 Bernhard Reutner-Fischer
2011-05-10 16:18 ` x86_64 Michael Smith
2011-05-10 17:51 ` x86_64 Phil Blundell
2011-05-10 18:43 ` x86_64 Bernhard Reutner-Fischer
2011-05-10 16:38 ` x86_64 Enrico Scholz
2011-05-10 20:30 ` x86_64 Phil Blundell
2011-05-11 10:07 ` x86_64 Enrico Scholz
2011-05-15 22:11 ` x86_64 Khem Raj
2011-05-16 11:08 ` x86_64 Phil Blundell
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=4DC9541B.6070208@nedap.com \
--to=jaap.dejong@nedap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox