From: Khem Raj <raj.khem@gmail.com>
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, 7 Jun 2011 10:43:07 -0700 [thread overview]
Message-ID: <BANLkTim4y6zp6nMOhNNhfxmZPdYuWjOimA@mail.gmail.com> (raw)
In-Reply-To: <1307439362.2529.4741.camel@phil-desktop>
On Tue, Jun 7, 2011 at 2:36 AM, Phil Blundell <pb@pbcl.net> wrote:
> Ping?
Both changes are fine.
change from being machine specific is futuristic it will not work for
all architectures that
uclibc supports but is sufficient for what we support/use in oe for now.
Acked-by: Khem Raj <raj.khem@gmail.com>
>
> 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
>
next prev parent reply other threads:[~2011-06-07 17:46 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 [this message]
2011-06-07 17:48 ` Koen Kooi
2011-06-07 17:59 ` Khem Raj
2011-06-07 20:36 ` Richard Purdie
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=BANLkTim4y6zp6nMOhNNhfxmZPdYuWjOimA@mail.gmail.com \
--to=raj.khem@gmail.com \
--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 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.