Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-cross: Explicitly depend on linux-libc-headers
Date: Fri, 23 Nov 2012 12:16:09 +0000	[thread overview]
Message-ID: <1353672970.13864.739.camel@phil-desktop> (raw)
In-Reply-To: <1353672077.1361.4.camel@ted>

On Fri, 2012-11-23 at 12:01 +0000, Richard Purdie wrote:
> I'm not sure "gratuitous" is entirely fair, the metadata as it stands
> today is fairly linux centric.

For some (maybe large) parts of the metadata that's probably true, but
gcc-cross does happen to be usable on non-linux with only minor
adjustments to EXTRA_OECONF and it would be nice to keep it that way.

>I will however change this to use anonymous python despite the
>performance and readability downsides 

Thank you.

>... since I appear to have hit some nerve.

I guess you could view it that way.  I am indeed sensitive to having my
builds broken in easily-avoidable ways. 

p.





  reply	other threads:[~2012-11-23 12:30 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
2012-11-23 10:16     ` Phil Blundell
2012-11-23 12:01       ` Richard Purdie
2012-11-23 12:16         ` Phil Blundell [this message]
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=1353672970.13864.739.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox