From: Sven Neumann <s.neumann@raumfeld.com>
To: buildroot@busybox.net
Subject: [Buildroot] build of e2fsprogs fails (2012.02-rc3)
Date: Tue, 28 Feb 2012 13:38:59 +0100 [thread overview]
Message-ID: <1330432739.2274.31.camel@sven> (raw)
In-Reply-To: <3d41058a0f241311e2b0fe5c2e3c9d1c@zacarias.com.ar>
Hi,
On Tue, 2012-02-28 at 09:11 -0300, Gustavo Zacarias wrote:
> > the build of e2fsprogs fails with 2012.02-rc3:
> >
> > CC e4defrag.c
> > e4defrag.c:28:17: fatal error: ftw.h: No such file or directory
> > compilation terminated.
>
> What about your uclibc config?
> If you're using a custom uclibc config basically "you're on your own"
> if packages break.
> Like on bug #4736 you reported.
> Packages are tested to work on buildroot's-shipped default uclibc
> configurations.
> At least that's my take.
Well, this probably used to be a default uclibc configuration three
years ago. Since then we have updated buildroot several times and
obviously our ubclibc configuration diverged. What would be the best way
to go back to the default uclibc configuration?
Nevertheless, you should consider the patch I've sent as the
BR2_PACKAGE_E2FSPROGS_E4DEFRAG option is currently not correctly
handled.
Regards,
Sven
next prev parent reply other threads:[~2012-02-28 12:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 11:16 [Buildroot] build of e2fsprogs fails (2012.02-rc3) Sven Neumann
2012-02-28 11:22 ` [Buildroot] [PATCH] e2fsprogs: disable build of e4defrag unless explicitly enabled Sven Neumann
2012-02-28 19:53 ` Peter Korsgaard
2012-02-28 12:11 ` [Buildroot] build of e2fsprogs fails (2012.02-rc3) Gustavo Zacarias
2012-02-28 12:38 ` Sven Neumann [this message]
2012-02-28 12:49 ` Gustavo Zacarias
2012-02-28 12:54 ` Sven Neumann
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=1330432739.2274.31.camel@sven \
--to=s.neumann@raumfeld.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