From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] package/uclibc: enable wordexp
Date: Thu, 6 Nov 2014 18:45:04 +0100 [thread overview]
Message-ID: <20141106184504.3133a975@free-electrons.com> (raw)
In-Reply-To: <545BAF17.2090009@zacarias.com.ar>
Dear Gustavo Zacarias,
On Thu, 06 Nov 2014 14:25:43 -0300, Gustavo Zacarias wrote:
> Yes, that's true.
> The series is RFC, i can add an exception for external toolchains, or
> alternatively just disable this for uClibc in general - after all
> enabling all the big versions is bloaty enough.
I just had a look at ifupdown source code, and wordexp() is pretty
central in the code, not sure we can easily replace it with something
else without significantly patching the stuff.
I don't really have a good answer here. Maybe as you suggest disabling
ifupdown entirely for uClibc toolchains? I've also checked
Crosstool-NG, and all its default uClibc configuration files have
wordexp disabled, so both Buildroot pre-built toolchains predating the
wordexp addition and all Crosstool-NG uClibc toolchain would be
affected by the problem.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-11-06 17:45 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 13:36 [Buildroot] [PATCH 0/7] [RFC] systemV init without busybox series Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 1/7] skeleton/S40network: tweak for debian ifupdown Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 2/7] package/uclibc: enable wordexp Gustavo Zacarias
2014-11-06 17:22 ` Thomas Petazzoni
2014-11-06 17:25 ` Gustavo Zacarias
2014-11-06 17:45 ` Thomas Petazzoni [this message]
2014-11-06 17:48 ` Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 3/7] dhcpcd: install binary to /sbin Gustavo Zacarias
2014-11-07 13:42 ` Vicente Olivert Riera
2014-11-06 13:36 ` [Buildroot] [PATCH 4/7] dhcpcd: bump to version 6.6.0 Gustavo Zacarias
2014-11-07 13:42 ` Vicente Olivert Riera
2014-11-06 13:36 ` [Buildroot] [PATCH 5/7] dash: bump to 0.5.8-2 Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 6/7] debianutils: new package Gustavo Zacarias
2014-11-06 13:36 ` [Buildroot] [PATCH 7/7] ifupdown: " Gustavo Zacarias
2014-11-06 18:00 ` Danomi Manchego
2014-11-06 18:10 ` Gustavo Zacarias
2014-11-06 18:12 ` Thomas Petazzoni
2014-11-06 18:34 ` Gustavo Zacarias
2014-11-06 17:24 ` [Buildroot] [PATCH 0/7] [RFC] systemV init without busybox series Thomas Petazzoni
2014-11-06 17:32 ` Gustavo Zacarias
2014-11-07 9:12 ` Károly Kasza
2014-11-07 10:07 ` Gustavo Zacarias
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=20141106184504.3133a975@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox