From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] SDK confusion Was: [meta-oe] gdb-cross-canadian: build gdb with python support
Date: Fri, 3 Feb 2012 14:52:06 +0100 [thread overview]
Message-ID: <20120203145206.10e943eb@eb-e6520> (raw)
In-Reply-To: <20120203114451.GF3893@jama.jama.net>
Le Fri, 3 Feb 2012 12:44:51 +0100,
Martin Jansa <martin.jansa@gmail.com> a écrit :
> I also don't really understand using oecore-x86_64-x86_64 when building
> for qemuarm
>
I may be totally wrong but isn't that what is expected : building a gdb
which will run on the SDK_ARCH (ie x86_64 in my case), so isn't python
expected to run on the x86_64 and target x86_64 (and not arm) ?
Eric
--
http://eukrea.com/en/news/104-2012
WARNING: multiple messages have this Message-ID (diff)
From: "Eric Bénard" <eric@eukrea.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] SDK confusion Was: [meta-oe] gdb-cross-canadian: build gdb with python support
Date: Fri, 3 Feb 2012 14:52:06 +0100 [thread overview]
Message-ID: <20120203145206.10e943eb@eb-e6520> (raw)
In-Reply-To: <20120203114451.GF3893@jama.jama.net>
Le Fri, 3 Feb 2012 12:44:51 +0100,
Martin Jansa <martin.jansa@gmail.com> a écrit :
> I also don't really understand using oecore-x86_64-x86_64 when building
> for qemuarm
>
I may be totally wrong but isn't that what is expected : building a gdb
which will run on the SDK_ARCH (ie x86_64 in my case), so isn't python
expected to run on the x86_64 and target x86_64 (and not arm) ?
Eric
--
http://eukrea.com/en/news/104-2012
next prev parent reply other threads:[~2012-02-03 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 7:12 [meta-oe] gdb-cross-canadian: build gdb with python support Eric Bénard
2011-12-23 11:02 ` Otavio Salvador
2012-01-04 5:18 ` Khem Raj
2012-01-04 8:05 ` Eric Bénard
2012-02-02 7:45 ` Martin Jansa
2012-02-02 8:06 ` Eric Bénard
2012-02-02 8:40 ` Martin Jansa
2012-02-02 9:17 ` Martin Jansa
2012-02-02 10:11 ` Eric Bénard
2012-02-03 7:28 ` Martin Jansa
2012-02-03 9:41 ` SDK confusion Was: [oe] " Martin Jansa
2012-02-03 9:41 ` SDK confusion Was: " Martin Jansa
2012-02-03 10:20 ` [oe] " Eric Bénard
2012-02-03 10:20 ` Eric Bénard
2012-02-03 11:44 ` [oe] " Martin Jansa
2012-02-03 11:44 ` [OE-core] " Martin Jansa
2012-02-03 13:52 ` Eric Bénard [this message]
2012-02-03 13:52 ` Eric Bénard
2012-02-02 8:58 ` Eric Bénard
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=20120203145206.10e943eb@eb-e6520 \
--to=eric@eukrea.com \
--cc=openembedded-core@lists.openembedded.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.