From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 6704] New: wpa_supplicant: fix wrong path to executable file in D-Bus
Date: Sat, 16 Nov 2013 23:35:34 +0000 (UTC) [thread overview]
Message-ID: <bug-6704-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=6704
Summary: wpa_supplicant: fix wrong path to executable file in
D-Bus
Product: buildroot
Version: unspecified
Platform: All
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: sasamy at yandex.ru
CC: buildroot at uclibc.org
Estimated Hours: 0.0
By default prefix is set to /usr/local
wpa_supplicant-2.0/wpa_supplicant/Makefile
export LIBDIR ?= /usr/local/lib/
export BINDIR ?= /usr/local/sbin/
but should be /usr/lib and /usr/sbin, can be corrected by specifying
environment variables
define WPA_SUPPLICANT_BUILD_CMDS
$(TARGET_MAKE_ENV) CFLAGS="$(WPA_SUPPLICANT_CFLAGS)" \
LDFLAGS="$(TARGET_LDFLAGS)" LIBDIR=/usr/lib/ BINDIR=/usr/sbin/
\
$(MAKE) CC="$(TARGET_CC)" -C $(@D)/$(WPA_SUPPLICANT_SUBDIR)
endef
These variables are used for generating service files for ?-Bus and Systemd
[D-BUS Service]
Name=fi.w1.wpa_supplicant1
Exec=@BINDIR@/wpa_supplicant -u
User=root
SystemdService=wpa_supplicant.service
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2013-11-16 23:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-16 23:35 bugzilla at busybox.net [this message]
2013-11-28 19:57 ` [Buildroot] [Bug 6704] wpa_supplicant: fix wrong path to executable file in D-Bus bugzilla at busybox.net
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=bug-6704-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.