All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 23 Nov 2012 15:44:40 +0000	[thread overview]
Message-ID: <1353685480.1361.14.camel@ted> (raw)
In-Reply-To: <1353672970.13864.739.camel@phil-desktop>

On Fri, 2012-11-23 at 12:16 +0000, Phil Blundell wrote:
> 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. 

I think the problem is that I can't reasonably know that you (or others)
are using the gcc-cross recipe for non-linux purposes. I've never seen
patches related to that or any other sign of it.

I now know this so I will try to account for it and the multitude of
other things I try and account for in future. You have implied this is
easily avoidable and it is, *if* you know what it is you're trying to
avoid (and can remember all of them).

Cheers,

Richard





  reply	other threads:[~2012-11-23 15:59 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
2012-11-23 15:44           ` Richard Purdie [this message]
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=1353685480.1361.14.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.