All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: kevin.strasser@linux.intel.com
Cc: Holger Hans Peter Freyther <holger@moiji-mobile.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] archiver.bbclass: Archive the native builds as well
Date: Fri, 18 Jan 2013 10:35:51 -0800	[thread overview]
Message-ID: <50F99607.3080902@linux.intel.com> (raw)
In-Reply-To: <59506.10.252.133.156.1358533499.squirrel@linux.intel.com>

On 01/18/2013 10:24 AM, kevin.strasser@linux.intel.com wrote:
>> On my build no copy of gcc/opkg-utils was archived. For gcc it is
>> bad as libgcc will end up in the image and the sources should be
>> provided. Update the method and comment to not exclude the native
>> version of the build.
>
> Native packages shouldn't be included in the target image, and therefor do
>not need to have their sources archived for any compliance purposes.
>

Correct, but in this case the gcc package provides the libgcc libraries 
on the target, GCC is a special case since it's source in the 
work-shared directory. There is a libgcc in work/<arch>/libgcc, but it 
only contains the build, the sources are all in the work-shared/gcc dir.

Sau!

> -Kevin
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>



  reply	other threads:[~2013-01-18 18:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18 14:34 [PATCH] archiver.bbclass: Archive the native builds as well Holger Hans Peter Freyther
2013-01-18 18:24 ` kevin.strasser
2013-01-18 18:35   ` Saul Wold [this message]
2013-01-18 18:25 ` Saul Wold
2013-01-19  8:44   ` Holger Hans Peter Freyther
2013-01-20 12:56     ` Richard Purdie
2013-01-20 15:47       ` Holger Hans Peter Freyther

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=50F99607.3080902@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=holger@moiji-mobile.com \
    --cc=kevin.strasser@linux.intel.com \
    --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.