Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add host-libglib2 dependencie to dbus-glib
Date: Wed, 22 Apr 2009 16:34:23 +0200	[thread overview]
Message-ID: <87zle8oiz4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <49EF2669.7010607@eclis.ch> (Jean-Christian de Rivaz's message of "Wed\, 22 Apr 2009 16\:15\:05 +0200")

>>>>> "Jean-Christian" == Jean-Christian de Rivaz <jc@eclis.ch> writes:

 >> 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.

 Jean-Christian> Interesting. On ARM I can only build dbus with expat.

 Jean-Christian> BR2_PACKAGE_DBUS=y
 Jean-Christian> BR2_DBUS_EXPAT=y
 Jean-Christian> # BR2_DBUS_LIBXML2 is not set
 Jean-Christian> BR2_PACKAGE_DBUS_GLIB=y

What happens when you try building it with libxml2? I fixed a build
issue with libxml2 in February.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2009-04-22 14:34 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
2009-04-22 14:27       ` Sven Neumann
2009-04-22 14:34       ` Peter Korsgaard [this message]
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=87zle8oiz4.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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