Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hadrien Boutteville <hadrien.boutteville@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Bump packages before adding libgtk3
Date: Thu, 19 Jun 2014 17:44:34 +0200	[thread overview]
Message-ID: <53A30562.3050005@gmail.com> (raw)
In-Reply-To: <20140619143704.14a3fa8e@free-electrons.com>

Hi Eric, Thomas,

On Thu, 19 Jun 2014 14:37:04 +0200, Thomas Petazzoni wrote:
> Dear Eric Le Bihan,
> 
> On Thu, 19 Jun 2014 10:02:49 +0200, Eric Le Bihan wrote:
> 
>> I also have a WIP packaging for libgtk3 [1]
> 
> Aah, ok. Then please sync with Hadrien on how to upstream this and
> avoid duplicated work.

Great! I'm looking at your branch. You can find mine here:
https://github.com/Eksel/buildroot/tree/libgtk3
(warning, WIP, there are ugly commits and there will be some rebase soon
;-) ).

Apparently we did several things differently, like how to handle the
host-libgtk3 build (I just adapted the patch from libgtk2).

>> , but I have not sent the
>> patch because libgtk3 depends on at-spi2-core. This package performs
>> some non-cross-compilable checks in its configure script via this m4
>> macro, defined in acinclude.m4:
>>
>>   DBIND_CHECK_ALIGNOF(dbus_bool_t)
>>
>> It fails when cross-compiling because it relies on AC_TRY_RUN() [2].
>>
>> The only (ugly) solution I found was hardcoding some values depending
>> on the architecture [3]:
>>
>>   ifeq ($(BR2_i386), y)
>>   AT_SPI2_CORE_CONF_ENV = ac_cv_alignof_char=1 \
>>   	ac_cv_alignof_double=4 \
>>   	ac_cv_alignof_dbind_pointer=4 \
>>   	ac_cv_alignof_dbind_struct=1 \
>>   	ac_cv_alignof_dbus_bool_t=4 \
>>   	ac_cv_alignof_dbus_int16_t=2 \
>>   	ac_cv_alignof_dbus_int32_t=4 \
>>   	ac_cv_alignof_dbus_int64_t=4
>>   endif
>>
>> How do you deal with this problem?
> 
> AC_CHECK_ALIGNOF() ?

Well, I didn't find (yet) the at-spi2-core dependency, so I don't have
this problem for now. I'm still resolving some configure errors.
It's a bit weird, there is no references to at-spi2-* neither in the
documentation nor in the configure.

Best regards,

Hadrien

      reply	other threads:[~2014-06-19 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 16:19 [Buildroot] [PATCH 0/3] Bump packages before adding libgtk3 Hadrien Boutteville
2014-06-18 16:19 ` [Buildroot] [PATCH 1/3] libglib2: bump to version 2.40.0 Hadrien Boutteville
2014-06-18 20:08   ` Thomas De Schampheleire
2014-06-19 15:02     ` Hadrien Boutteville
2014-06-18 16:19 ` [Buildroot] [PATCH 2/3] pango: bump to version 1.36.3 Hadrien Boutteville
2014-06-18 20:10   ` Thomas De Schampheleire
2014-06-18 16:19 ` [Buildroot] [PATCH 3/3] cairo: add freetype dependency for freetype support Hadrien Boutteville
2014-06-19  8:02 ` [Buildroot] [PATCH 0/3] Bump packages before adding libgtk3 Eric Le Bihan
2014-06-19 12:37   ` Thomas Petazzoni
2014-06-19 15:44     ` Hadrien Boutteville [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=53A30562.3050005@gmail.com \
    --to=hadrien.boutteville@gmail.com \
    --cc=buildroot@busybox.net \
    /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