From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2012-12-30
Date: Mon, 31 Dec 2012 18:12:24 +0100 [thread overview]
Message-ID: <20121231181224.4326dab6@skate> (raw)
In-Reply-To: <201212311257.38291.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Mon, 31 Dec 2012 12:57:38 +0100, Yann E. MORIN wrote:
> I think we should do 2: packages in buildroot should at least all (except
> maybe some platform-specific packages that may require an external
> toolchain, eg. bfin and ?blaze) build with the internal toolchain
> mechanism.
>
> What do you think?
Another option: identify *why* wordexp is needed. I just had a quick
look: only src/epggrab.c includes <wordexp.h>. It doesn't use wordexp()
and wordfree() and apparently none of the definitions I have in my
glibc wordexp.h.
Can you try to build with the #include <wordexp.h> removed?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-12-31 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 7:35 [Buildroot] [autobuild.buildroot.net] Build results for 2012-12-30 Thomas Petazzoni
2012-12-31 11:57 ` Yann E. MORIN
2012-12-31 17:12 ` Thomas Petazzoni [this message]
2012-12-31 18:19 ` Yann E. MORIN
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=20121231181224.4326dab6@skate \
--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 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.