Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gtk+ build failure after create_wrapper commit
Date: Sun, 03 Oct 2010 21:38:07 +0200	[thread overview]
Message-ID: <i8am2v$c76$1@dough.gmane.org> (raw)
In-Reply-To: <AANLkTimmq=tcfb_x_S5T4Jp3UXFR7hdofO7arBXvPeKL@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03-10-10 20:39, Chris Larson wrote:
> On Sun, Oct 3, 2010 at 8:25 AM, Chris Larson <clarson@kergoth.com> wrote:
> 
>>
>>
>> On Sun, Oct 3, 2010 at 2:26 AM, Koen Kooi <k.kooi@student.utwente.nl>wrote:
>>
>>> Last nights build failed with:
>>>
>>> | make[2]: Entering directory
>>>
>>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gtk+-2.20.1-r9.3/gtk+-2.20.1/demos'
>>> | /OE/angstrom-dev/sysroots/x86_64-linux/usr/bin/gdk-pixbuf-csource
>>> - --raw --build-list          \
>>> |               apple_red  ./apple-red.png      \
>>> |                 gnome_foot ./gnome-foot.png   \
>>> |         > test-inline-pixbufs.h                               \
>>> |       || (rm -f test-inline-pixbufs.h && false)
>>> | Usage: gdk-pixbuf-csource [options] [image]
>>> |        gdk-pixbuf-csource [options] --build-list [[name image]...]
>>> |   --stream                   generate pixbuf data stream
>>> |   --struct                   generate GdkPixdata structure
>>> |   --macros                   generate image size/pixel macros
>>> |   --rle                      use one byte run-length-encoding
>>> |   --raw                      provide raw image data copy
>>> |   --extern                   generate extern symbols
>>> |   --static                   generate static symbols
>>> |   --decoder                  provide rle decoder
>>> |   --name=identifier          C macro/variable name
>>> |   --build-list               parse (name, image) pairs
>>> |   -h, --help                 show this help message
>>> |   -v, --version              print version informations
>>> |   --g-fatal-warnings         make warnings fatal (abort)
>>> | make[2]: *** [test-inline-pixbufs.h] Error 1
>>> | make[2]: Leaving directory
>>>
>>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gtk+-2.20.1-r9.3/gtk+-2.20.1/demos'
>>> | make[1]: *** [all-recursive] Error 1
>>> | make[1]: Leaving directory
>>>
>>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/gtk+-2.20.1-r9.3/gtk+-2.20.1'
>>> | make: *** [all] Error 2
>>>
>>> I'll have a better look at work tomorrow, but if anyone has a fix ready,
>>> don't hesitate to speak up :)
>>>
>>
>> Reverted for now, working on a fix.  Sorry about that.  Must have missed
>> something obvious.
>>
> 
> Fixed, confirmed gtk+ builds with it.  Sorry for the hassle.

Thanks for the quick fix! Looking at the fix I can certainly say that it
wouldn't have occured to me to check wether the wrapper passed args or
not :)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMqNufMkyGM64RGpERAtv0AJwL6NrbJ+HhhHjgWB3bPQ7ai8biXwCgqgu6
1CtgwvTmXrx3tDhV/CNjgcA=
=27Cv
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-10-03 19:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-03  9:26 gtk+ build failure after create_wrapper commit Koen Kooi
2010-10-03 15:25 ` Chris Larson
2010-10-03 18:39   ` Chris Larson
2010-10-03 19:38     ` Koen Kooi [this message]
2010-10-03 20:23     ` Koen Kooi

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='i8am2v$c76$1@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox