From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64
Date: Tue, 10 May 2011 17:35:43 +0200 [thread overview]
Message-ID: <lyiptilga8.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <4DC9541B.6070208@nedap.com> (Jaap de Jong's message of "Tue, 10 May 2011 17:04:59 +0200")
Jaap de Jong <jaap.dejong@nedap.com> writes:
> TARGET_ARCH = "x86_64"
did this ever work? OE uses hardcoded 'lib' (instead of 'lib64') at
various places. At least gcc has
| #define GLIBC_DYNAMIC_LINKER64 "/lib64/ld-linux-x86-64.so.2"
which causes 64 bit binaries to look for the interpreter at /lib64.
I recall issues with openssl too which autodetects lib64 directories but
OE packages lib only.
Enrico
next prev parent reply other threads:[~2011-05-10 15:38 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 ` x86_64 Jaap de Jong
2011-05-10 15:35 ` Enrico Scholz [this message]
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=lyiptilga8.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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