From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libx11-trim: update to 1.4.4
Date: Wed, 23 Nov 2011 23:16:39 +0000 [thread overview]
Message-ID: <1322090199.15626.21.camel@ted> (raw)
In-Reply-To: <CAMKF1sojEYRJE15kic3JHjXCH=MCDUZGhRYKBMSYVmvEhhE_=g@mail.gmail.com>
On Wed, 2011-11-23 at 14:15 -0800, Khem Raj wrote:
> On Mon, Nov 21, 2011 at 12:32 AM, Xiaofeng Yan
> <xiaofeng.yan@windriver.com> wrote:
> > +++ b/meta/recipes-graphics/xorg-lib/libx11-trim-1.4.4/makekeys_crosscompile.patch
> > @@ -0,0 +1,45 @@
> > +Because the size of "unsigned long" is different between 32-bit
> > +and 64-bit, judge whether target is 32-bit or 64-bit and tell
> > +"makekey".
> > +
> > +Upstream-Status: Pending
> > +
> > +Signed-off-by: dbuitenh@windriver.com
> > +
> > +--- libX11-1.3.4.orig/src/util/makekeys.c 2010-01-15 09:11:36.000000000 +0800
> > ++++ libX11-1.3.4/src/util/makekeys.c 2011-05-24 19:04:25.454774908 +0800
> > +@@ -33,6 +33,7 @@
> > + #include <X11/keysymdef.h>
> > + #include <stdio.h>
> > + #include <stdlib.h>
> > ++#include <stdint.h>
> > +
> > + typedef unsigned long Signature;
> > +
> > +@@ -124,7 +125,12 @@
> > + name = info[i].name;
> > + sig = 0;
> > + while ((c = *name++))
> > +- sig = (sig << 1) + c;
> > ++#ifdef USE32
> > ++ sig = (uint32_t)(sig << 1) + c;
> > ++#else
> > ++ sig = (uint64_t)(sig << 1) + c;
> > ++#endif
> > ++
> > + first = j = sig % z;
> > + for (k = 0; tab[j]; k++) {
> > + j += first + 1;
> > +@@ -163,7 +169,11 @@
> > + name = info[i].name;
> > + sig = 0;
> > + while ((c = *name++))
> > +- sig = (sig << 1) + c;
> > ++#ifdef USE32
> > ++ sig = (uint32_t)(sig << 1) + c;
> > ++#else
> > ++ sig = (uint64_t)(sig << 1) + c;
> > ++#endif
> > + first = j = sig % z;
> > + while (offsets[j]) {
> > + j += first + 1;
>
> why use USE32 define ? why not use compiler builtin define __LP64__ ?
> is it something a programs that needs to know the bitness of target or
> something ?
This gets run on the build system but needs to generate data for the
target...
Cheers,
Richard
next prev parent reply other threads:[~2011-11-23 23:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 8:29 [PATCH 0/1] libx11-trim: update to 1.4.4 Xiaofeng Yan
2011-11-21 8:29 ` [PATCH 1/1] blibx11-trim: " Xiaofeng Yan
2011-11-23 22:15 ` [PATCH 1/1] libx11-trim: " Khem Raj
2011-11-23 23:16 ` Richard Purdie [this message]
2011-11-29 16:00 ` [PATCH 0/1] " Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2011-11-17 11:00 Xiaofeng Yan
2011-11-17 11:00 ` [PATCH 1/1] " Xiaofeng Yan
2011-11-17 11:24 ` Martin Jansa
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=1322090199.15626.21.camel@ted \
--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