Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Holger Freyther <holger+oe@freyther.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Remove dbus support from wvstreams-4.6 because it breaks the build
Date: Tue, 28 Sep 2010 16:19:50 +0800	[thread overview]
Message-ID: <4CA1A526.5000209@freyther.de> (raw)
In-Reply-To: <1285658920-15596-1-git-send-email-t.fromm@dresearch.de>

On 09/28/2010 03:28 PM, Thilo Fromm wrote:

> 
> This patch, however, does not fix the configure.ac file but disables
> DBus support for wvstreams at configure time. This at least fixes the
> broken build.

well, then don't add extra depends on dbus? Otherwise it seems fine for now to
disable dbus support.


> -DEPENDS = "zlib openssl (>= 0.9.8)"
> +DEPENDS = "zlib openssl (>= 0.9.8) dbus (> 1.2.14)"
>  



      parent reply	other threads:[~2010-09-28  8:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-28  7:28 [PATCH] Remove dbus support from wvstreams-4.6 because it breaks the build Thilo Fromm
2010-09-28  7:49 ` Paul Menzel
2010-09-28  8:12   ` [v2] wvstreams-4.6: Remove dbus support " Thilo Fromm
2010-09-28  8:33     ` Paul Menzel
2010-09-28  9:08       ` Thilo Fromm
2010-09-28  9:24         ` Thilo Fromm
2010-09-28  9:26         ` Paul Menzel
2010-09-28  9:34           ` [v4] wvstreams-4.6: Remove dbus support (breaks build) Thilo Fromm
2010-09-29  8:20             ` Paul Menzel
2010-09-29  8:52               ` Thilo Fromm
2010-09-29  8:56                 ` Paul Menzel
2010-09-29  9:15               ` Steffen Sledz
2010-09-28  9:37           ` [v2] wvstreams-4.6: Remove dbus support because it breaks the build Thilo Fromm
2010-09-28 11:05         ` Steffen Sledz
2010-09-28  9:21       ` [v3] wvstreams-4.6: Remove dbus support (breaks build) Thilo Fromm
2010-09-28  8:10 ` [PATCH] Remove dbus support from wvstreams-4.6 because it breaks the build Frans Meulenbroeks
2010-09-28  9:10   ` Thilo Fromm
2010-09-28  8:19 ` Holger Freyther [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=4CA1A526.5000209@freyther.de \
    --to=holger+oe@freyther.de \
    --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