From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: how can i ask to keep all the generated "nativesdk" rpms?
Date: Wed, 19 Oct 2016 23:11:32 +0100 [thread overview]
Message-ID: <1476915092.2166.105.camel@linuxfoundation.org> (raw)
In-Reply-To: <alpine.LFD.2.20.1610191733110.26015@localhost.localdomain>
On Wed, 2016-10-19 at 17:34 -0400, Robert P. J. Day wrote:
> so, i'm home and on a different system about to do a build ...
> refresh my memory, where are all those nativesdk rpms supposed to
> show
> up? if memory serves, they were under tmp/deploy/rpm/x86_64_linux.
> anything i should set before i attempt a build?
For SDKMACHINE="x86_64", the would appear in:
tmp/deploy/rpm/x86_64_nativesdk/
and SDKMACHINE="i686" in:
tmp/deploy/rpm/i686_nativesdk/
Switching SDKMACHINE might have been a trigger for one set
disappearing, particularly on older versions. Which version was this?
There were some bugs fixed in master/morty related to it.
Cheers,
Richard
next prev parent reply other threads:[~2016-10-19 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-19 15:14 how can i ask to keep all the generated "nativesdk" rpms? Robert P. J. Day
2016-10-19 15:27 ` Robert P. J. Day
2016-10-19 19:28 ` Paul Eggleton
2016-10-19 19:32 ` Robert P. J. Day
2016-10-19 19:39 ` Paul Eggleton
2016-10-19 19:42 ` Robert P. J. Day
2016-10-19 19:52 ` Paul Eggleton
2016-10-19 21:34 ` Robert P. J. Day
2016-10-19 22:11 ` Richard Purdie [this message]
2016-10-19 22:17 ` Robert P. J. Day
2016-10-20 10:31 ` Robert P. J. Day
2016-10-20 10:45 ` Richard Purdie
2016-10-20 11:12 ` Robert P. J. Day
2016-10-20 11:02 ` Burton, Ross
2016-10-19 22:09 ` Richard Purdie
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=1476915092.2166.105.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=rpjday@crashcourse.ca \
/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