From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFH] Native SDK wirdness
Date: Tue, 28 Jun 2011 17:16:49 +0100 [thread overview]
Message-ID: <1309277809.20015.322.camel@rex> (raw)
In-Reply-To: <BANLkTi=GQS+Rwv+srtcctpD3jDwu7RWv2Q@mail.gmail.com>
On Tue, 2011-06-28 at 11:56 -0300, Otavio Salvador wrote:
> I am probably doing something stupid but I couldn't figure it myself
> so I am looking for some help here. Basically I need to prepare a SDK
> for usage by our team mates to develop to our embedded OS. In theory I
> got most of it already done but when I build the meta-toolchain recipe
> the built sdk tarball lacks GCC and like.
>
> Any idea where I ought to look for a good example? Or any clue what I
> am doing wrong?
Could you share a list of files from your toolchain tarball please? It
certainly should contain a cross compiler...
Cheers,
Richard
next prev parent reply other threads:[~2011-06-28 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-28 14:56 [RFH] Native SDK wirdness Otavio Salvador
2011-06-28 16:16 ` Richard Purdie [this message]
2011-06-28 16:27 ` Otavio Salvador
2011-06-28 21:31 ` Zhang, Jessica
2011-06-28 23:58 ` 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=1309277809.20015.322.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@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.