All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [STABLE][PATCH] linux-libc-headers_2.6.23.bb : more modern glibc expose getline from
Date: Thu, 07 May 2009 08:21:03 -0400	[thread overview]
Message-ID: <4A02D22F.9000703@balister.org> (raw)
In-Reply-To: <gtugca$fk0$1@ger.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3002 bytes --]

Acked-by; Philip Balister <philip@balister.org>

Thanks to Graeme for taking the time to explain this. This is needed to 
use OE on machines with a recent glibc.

Philip

Koen Kooi wrote:
> ping
> 
> On 28-04-09 16:36, Koen Kooi wrote:
>> From: Graeme Gregory<dp@xora.org.uk>
>>
>>
>> Signed-off-by: Koen Kooi<koen@openembedded.org>
>> ---
>>   recipes/linux-libc-headers/files/unifdef.patch     |   31 
>> ++++++++++++++++++++
>>   .../linux-libc-headers_2.6.23.bb                   |    5 ++-
>>   2 files changed, 34 insertions(+), 2 deletions(-)
>>   create mode 100644 recipes/linux-libc-headers/files/unifdef.patch
>>
>> diff --git a/recipes/linux-libc-headers/files/unifdef.patch 
>> b/recipes/linux-libc-headers/files/unifdef.patch
>> new file mode 100644
>> index 0000000..800c3c8
>> --- /dev/null
>> +++ b/recipes/linux-libc-headers/files/unifdef.patch
>> @@ -0,0 +1,31 @@
>> +Index: linux-2.6.23/scripts/unifdef.c
>> +===================================================================
>> +--- linux-2.6.23.orig/scripts/unifdef.c
>> ++++ linux-2.6.23/scripts/unifdef.c
>> +@@ -206,7 +206,7 @@ static void             done(void);
>> + static void             error(const char *);
>> + static int              findsym(const char *);
>> + static void             flushline(bool);
>> +-static Linetype         getline(void);
>> ++static Linetype         parseline(void);
>> + static Linetype         ifeval(const char **);
>> + static void             ignoreoff(void);
>> + static void             ignoreon(void);
>> +@@ -512,7 +512,7 @@ process(void)
>> +
>> +     for (;;) {
>> +         linenum++;
>> +-        lineval = getline();
>> ++        lineval = parseline();
>> +         trans_table[ifstate[depth]][lineval]();
>> +         debug("process %s ->  %s depth %d",
>> +             linetype_name[lineval],
>> +@@ -526,7 +526,7 @@ process(void)
>> +  * help from skipcomment().
>> +  */
>> + static Linetype
>> +-getline(void)
>> ++parseline(void)
>> + {
>> +     const char *cp;
>> +     int cursym;
>> diff --git a/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb 
>> b/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
>> index 13579f9..95152f1 100644
>> --- a/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
>> +++ b/recipes/linux-libc-headers/linux-libc-headers_2.6.23.bb
>> @@ -2,10 +2,11 @@ require linux-libc-headers.inc
>>
>>   INHIBIT_DEFAULT_DEPS = "1"
>>   DEPENDS += "unifdef-native"
>> -PR = "r3"
>> +PR = "r4"
>>
>>   SRC_URI = 
>> "${KERNELORG_MIRROR}/pub/linux/kernel/v2.6/linux-${PV}.tar.bz2 \
>> -           file://procinfo.h"
>> +           file://procinfo.h \
>> +           file://unifdef.patch;patch=1"
>>
>>   S = "${WORKDIR}/linux-${PV}"
>>
> 
> 
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
> 

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

      reply	other threads:[~2009-05-07 12:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28 14:36 [STABLE][PATCH] linux-libc-headers_2.6.23.bb : more modern glibc expose getline from Koen Kooi
2009-05-07 11:23 ` Koen Kooi
2009-05-07 12:21   ` Philip Balister [this message]

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=4A02D22F.9000703@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@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.