All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean-Christian de Rivaz <jc@eclis.ch>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add host-libglib2 dependencie to dbus-glib
Date: Wed, 22 Apr 2009 16:15:05 +0200	[thread overview]
Message-ID: <49EF2669.7010607@eclis.ch> (raw)
In-Reply-To: <1240404749.7072.1.camel@sven>

Sven Neumann a ?crit :
> Hi,
> 
> On Wed, 2009-04-22 at 14:48 +0200, Steffen Schulz wrote:
> 
>> I just had the same problem when trying to compile trunk for i686.
>> However, after applying the fix I got an error about missing '-lexpat'.
>> Adding expat to the dependencies fixed that.
> 
> There is expat in the dependencies already:
> 
> ifeq ($(BR2_DBUS_EXPAT),y)
> DBUS_CONF_OPT += --with-xml=expat
> DBUS_DEPENDENCIES += expat
> else
> DBUS_CONF_OPT += --with-xml=libxml
> DBUS_DEPENDENCIES += libxml2
> endif
> 
> We are using libxml2, so I can't tell for sure if compiling dbus with
> expat is working or not. But it looks as if the dependencies are
> correct.

Interesting. On ARM I can only build dbus with expat.

BR2_PACKAGE_DBUS=y
BR2_DBUS_EXPAT=y
# BR2_DBUS_LIBXML2 is not set
BR2_PACKAGE_DBUS_GLIB=y

Jean-Christian de Rivaz

  parent reply	other threads:[~2009-04-22 14:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-26  9:10 [Buildroot] [PATCH] Add host-libglib2 dependencie to dbus-glib Jean-Christian de Rivaz
2009-04-22 12:48 ` Steffen Schulz
2009-04-22 12:52   ` Sven Neumann
2009-04-22 13:17     ` Steffen Schulz
2009-04-22 13:58       ` Sven Neumann
2009-04-22 14:15     ` Jean-Christian de Rivaz [this message]
2009-04-22 14:27       ` Sven Neumann
2009-04-22 14:34       ` Peter Korsgaard
2009-04-22 15:32         ` [Buildroot] How to incorporate linux kernel patch correctly Will Moore
2009-04-23  8:24         ` [Buildroot] [PATCH] Add host-libglib2 dependencie to dbus-glib Jean-Christian de Rivaz
2009-04-23  8:40           ` Peter Korsgaard
2009-04-23  8:57             ` Jean-Christian de Rivaz

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=49EF2669.7010607@eclis.ch \
    --to=jc@eclis.ch \
    --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 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.