From: Pierre <pinaraf@pinaraf.info>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] wpa_supplicant - Specify that old and new dbus are incompatible
Date: Wed, 28 Feb 2018 23:55:34 +0100 [thread overview]
Message-ID: <3603330.UGTkN10abk@peanuts2> (raw)
In-Reply-To: <87fu5kkfy0.fsf@dell.be.48ers.dk>
On Wednesday, February 28, 2018 9:38:31 PM CET Peter Korsgaard wrote:
> >>>>> "Pierre" == Pierre Ducroquet <pinaraf@pinaraf.info> writes:
> > Building wpa-supplicant with support for both DBus interfaces
> > generates broken .service files.
>
> In what way are they broken? I did a quick test build of 3
> configurations:
>
> - Only old
> - Only new
> - Old and new
>
> and I don't see any difference in the .service files?
It generated a .service file with an empty BusName in the [Service] part of
the .service.
Since enabling only one interface generated the proper file, I deduced both
could not be enabled together. Maybe something else in my configuration
impacted that, I will check that again if you can't reproduce.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180228/fb2c328f/attachment.asc>
next prev parent reply other threads:[~2018-02-28 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 21:50 [Buildroot] [PATCH 1/1] wpa_supplicant - Specify that old and new dbus are incompatible Pierre Ducroquet
2018-02-28 20:38 ` Peter Korsgaard
2018-02-28 22:55 ` Pierre [this message]
2018-03-01 7:35 ` Peter Korsgaard
2018-12-16 13:10 ` Thomas Petazzoni
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=3603330.UGTkN10abk@peanuts2 \
--to=pinaraf@pinaraf.info \
--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.