From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: x86_64 host -- never ending story
Date: Sat, 27 Sep 2008 10:27:05 -0400 [thread overview]
Message-ID: <48DE42B9.8040900@balister.org> (raw)
In-Reply-To: <48DE3D09.4090608@linuxdevelopment.de>
[-- Attachment #1: Type: text/plain, Size: 609 bytes --]
Robert Wörle wrote:
> Can one give a quick and brief explanation why using oe on a x86_64 host
> is sooo difficult.
> I am having always a hard time to setup oe and build on that ... many
> architectures break on glibc-native or such stuff lile avr32.
> i686-generic or even arm sometimes ?
>
> And maybe show a short example how to substitute the oe-native libs for
> the hosts owns !
I'm running on x86_64 without problems. Certainly, these machines are
more sensitive to use of host libraries/includes, but they work well for me.
What machine/distro are you building for?
Philip
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]
next prev parent reply other threads:[~2008-09-27 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 14:02 x86_64 host -- never ending story Robert Wörle
2008-09-27 14:27 ` Philip Balister [this message]
2008-09-27 14:36 ` Phil Blundell
2008-09-27 17:06 ` Robert Wörle
2008-09-30 0:37 ` 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=48DE42B9.8040900@balister.org \
--to=philip@balister.org \
--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.