From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Phil Blundell <philb@gnu.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-cross: Explicitly depend on linux-libc-headers
Date: Thu, 22 Nov 2012 22:02:59 +0000 [thread overview]
Message-ID: <1353621779.10459.67.camel@ted> (raw)
In-Reply-To: <1353621014.2000.16.camel@x121e.pbcl.net>
On Thu, 2012-11-22 at 21:50 +0000, Phil Blundell wrote:
> On Thu, 2012-11-22 at 21:36 +0000, Richard Purdie wrote:
> > -DEPENDS = "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}libc-for-gcc ${NATIVEDEPS}"
> > +DEPENDS = "virtual/${TARGET_PREFIX}binutils virtual/${TARGET_PREFIX}libc-for-gcc linux-libc-headers ${NATIVEDEPS}"
>
> gcc-cross isn't particularly specific to linux targets and ideally we
> don't want to be adding more linuxisms to the recipe. It is,
> admittedly, not entirely obvious how we could conveniently get that
> dependency added only for linux targets (since I don't think there's any
> existing OVERRIDE that's helpful here) but perhaps we should find a way
> to address that problem rather than just sticking it in unconditionally.
virtual/${TARGET_OS}-headers with a suitable provider entry?
I was assuming someone who cares about non-linux wouldn't find this
particularly hard to deal with...
Cheers,
Richard
next prev parent reply other threads:[~2012-11-22 22:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 21:36 [PATCH] gcc-cross: Explicitly depend on linux-libc-headers Richard Purdie
2012-11-22 21:50 ` Phil Blundell
2012-11-22 22:02 ` Richard Purdie [this message]
2012-11-23 10:16 ` Phil Blundell
2012-11-23 12:01 ` Richard Purdie
2012-11-23 12:16 ` Phil Blundell
2012-11-23 15:44 ` Richard Purdie
2012-11-23 16:08 ` Otavio Salvador
2012-11-27 20:08 ` McClintock Matthew-B29882
2012-11-28 6:46 ` 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=1353621779.10459.67.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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.