All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: Randy MacLeod <randy.macleod@windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: How to put a correct dependency with regards to gcc?
Date: Wed, 09 Sep 2015 09:05:17 +0200	[thread overview]
Message-ID: <1441782317.11229.7.camel@intel.com> (raw)
In-Reply-To: <55EF9D64.8000601@windriver.com>

On Tue, 2015-09-08 at 22:45 -0400, Randy MacLeod wrote:
> Maybe we have to fix gcc-source after all rather than use the
> EXCLUDE_WORLD change I made in:
>     https://bugzilla.yoctoproject.org/show_bug.cgi?id=7878
> Does your scheme work for the kernel source? See:
> 
> Search for "kernel-devsrc" here:
>   http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/68352

Also possibly related: 
https://bugzilla.yoctoproject.org/show_bug.cgi?id=7959

"archiver.bbclass: fails for linux--yocto when archiving patched source"

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2015-09-09  7:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-04 17:03 How to put a correct dependency with regards to gcc? Reshetova, Elena
2015-09-09  2:45 ` Randy MacLeod
2015-09-09  7:05   ` Patrick Ohly [this message]
2015-09-09 16:13     ` Reshetova, Elena
2015-09-09 16:09   ` Reshetova, Elena
2015-09-14 17:55     ` Randy MacLeod
2015-09-14 18:06       ` Reshetova, Elena
2015-09-16  2:37       ` Randy MacLeod
2015-09-16 16:52         ` Richard Purdie
2015-09-22 11:03           ` Reshetova, Elena
2015-09-22 11:09             ` Richard Purdie
2015-09-22 11:13               ` Reshetova, Elena
2015-09-16 16:43 ` 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=1441782317.11229.7.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=randy.macleod@windriver.com \
    /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.