From: Valentine Barshak <gvaxon@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openvpn: Fix paths to external utilities
Date: Mon, 01 Oct 2012 00:40:33 +0400 [thread overview]
Message-ID: <5068AE41.8030809@gmail.com> (raw)
In-Reply-To: <5068A57A.6060703@zacarias.com.ar>
On 10/01/2012 12:03 AM, Gustavo Zacarias wrote:
> On 09/30/12 15:11, Valentine Barshak wrote:
>
>> This sets paths to ifconfig, route, netstat and ip
>> in the target root filesystem.
>>
>> Otherwise the paths leak from the host and may not
>> match those on the target.
>>
>> Signed-off-by: Valentine Barshak <gvaxon@gmail.com>
>> ---
>> package/openvpn/openvpn.mk | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/package/openvpn/openvpn.mk b/package/openvpn/openvpn.mk
>> index 03eabcf..b7e13f5 100644
>> --- a/package/openvpn/openvpn.mk
>> +++ b/package/openvpn/openvpn.mk
>> @@ -6,7 +6,11 @@
>>
>> OPENVPN_VERSION = 2.2.2
>> OPENVPN_SITE = http://swupdate.openvpn.net/community/releases
>> -OPENVPN_CONF_OPT = --enable-small --disable-plugins
>> +OPENVPN_CONF_OPT = --enable-small --disable-plugins \
>> + --with-ifconfig-path=/sbin/ifconfig \
>> + --with-route-path=/sbin/route \
>> + --with-netstat-path=/bin/netstat \
>> + --with-iproute-path=/bin/ip
>
> And what happens if i install let's say iproute2 which provides a
> nicer/bigger /sbin/ip instead of using the busybox one?
> Regards.
>
You'll be surprised to see openvpn fail to find it :)
Unless you build on the latest fedora, which has this stuff in
/usr/sbin. So you won't see any difference, because it has failed to
find it before.
I'll submit new version with BR2_PACKAGE_IPROUTE2 check.
Thanks,
Val.
prev parent reply other threads:[~2012-09-30 20:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-30 18:11 [Buildroot] [PATCH] openvpn: Fix paths to external utilities Valentine Barshak
2012-09-30 20:03 ` Gustavo Zacarias
2012-09-30 20:40 ` Valentine Barshak [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=5068AE41.8030809@gmail.com \
--to=gvaxon@gmail.com \
--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.