From: Patrick Ohly <Patrick.Ohly@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Interest for x86_64 target?
Date: Sun, 21 Jan 2007 10:03:31 +0100 [thread overview]
Message-ID: <1169370211.4172.7.camel@ip6-localhost> (raw)
In-Reply-To: <c384c5ea0701201646v68ef3fcevf0f6905fd46b6a13@mail.gmail.com>
On Sun, 2007-01-21 at 01:46 +0100, Leon Woestenberg wrote:
> any of the OE devs interested in adding x86_64 target support?
>
> I am, but I cannot pull this off alone due to time restrictions.
> However, if there is a group of ppl willing to go forward on this, I
> am in.
FYI, if you search the list for "cross-compiling for x86_64" you will
find a thread about my building an SDK for x86_64. It required some
patches, recorded under [1]. The scope was pretty limited though (I only
need the EDS-DBus libs).
[1] http://bugs.openembedded.org/show_bug.cgi?id=1728
--
Bye, Patrick Ohly
--
Patrick.Ohly@gmx.de
http://www.estamos.de/
prev parent reply other threads:[~2007-01-21 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 0:46 Interest for x86_64 target? Leon Woestenberg
2007-01-21 9:03 ` Patrick Ohly [this message]
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=1169370211.4172.7.camel@ip6-localhost \
--to=patrick.ohly@gmx.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