Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] uclibc: remove PACKAGE_ARCH, fix compilation on i586
Date: Tue, 07 Jun 2011 21:36:27 +0100	[thread overview]
Message-ID: <1307478987.15712.60.camel@rex> (raw)
In-Reply-To: <1307439362.2529.4741.camel@phil-desktop>

On Tue, 2011-06-07 at 10:36 +0100, Phil Blundell wrote:
> Ping?

I'm not against this move at all but before this patch merges we should
really have a cleanup which removes the *.machine configuration files
from the uclibc recipe directory along with all the machine specific
overrides that are in use instead making them arch specific.

Any volunteers?

Cheers,

Richard


> p.
> 
> On Fri, 2011-06-03 at 12:55 +0100, Phil Blundell wrote:
> > There is no good reason for uclibc to be machine specific.  Remove local
> > assignment to PACKAGE_ARCH so that it gets the default target
> > architecture and bump PR for that change.
> > 
> > See http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003064.html
> > 
> > Also replace a chunk of anonymous python with a COMPATIBLE_HOST
> > declaration.
> > 
> > Signed-off-by: Phil Blundell <philb@gnu.org>
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  parent reply	other threads:[~2011-06-07 20:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-03 11:55 [PATCH] uclibc: remove PACKAGE_ARCH, fix compilation on i586 Phil Blundell
2011-06-07  9:36 ` Phil Blundell
2011-06-07 17:43   ` Khem Raj
2011-06-07 17:48     ` Koen Kooi
2011-06-07 17:59       ` Khem Raj
2011-06-07 20:36   ` Richard Purdie [this message]
2011-06-08  1:28     ` Khem Raj
2011-06-10 14:02     ` Phil Blundell
2011-06-07  9:38 ` Koen Kooi
2011-06-07 15:33 ` Saul Wold
2011-06-07 15:51   ` Phil Blundell
2011-06-07 15:59     ` Saul Wold
2011-06-07 16:00     ` Mark Hatle

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=1307478987.15712.60.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox