From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] util-linux: disable fallocate for avr32
Date: Mon, 04 Nov 2013 07:40:27 +0100 [thread overview]
Message-ID: <5277415B.10202@mind.be> (raw)
In-Reply-To: <20131103121711.4c67418f@skate>
On 03/11/13 12:17, Thomas Petazzoni wrote:
> Dear Yann E. MORIN,
>
> On Sun, 3 Nov 2013 12:06:13 +0100, Yann E. MORIN wrote:
>
[snip]
>> My preference would be to remove feature-patches, but that is really
>> gonna hurt newcomers (and may bite long-timers as well).
>
> I believe the only reasonable solutions are (alternatively, and the
> choice can be made differently per-package) :
>
> (1) Add patches to the package to avoid usage of unimplemented uClibc
> features (when possible)
>
> (2) Mark the packages as depends on !UCLIBC
If I may throw in yet another alternative: depend on a version of
uClibc. We can call our patched uClibc version 0.9.34. At least, this
still applies when there's a finally a uClibc release: we would then need
a mechanism to mark a package to depend on the new uClibc.
On second thought, this is probably still difficult to maintain and
equally difficult for user to use a buildroot-generated toolchain as an
external toolchain.
Regards,
Arnout
>
> Best regards,
>
> Thomas
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-11-04 6:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 9:56 [Buildroot] [PATCH] util-linux: disable fallocate for avr32 spdawson at gmail.com
2013-11-03 10:34 ` Thomas Petazzoni
2013-11-03 11:06 ` Yann E. MORIN
2013-11-03 11:17 ` Thomas Petazzoni
2013-11-04 6:40 ` Arnout Vandecappelle [this message]
2013-11-10 23:41 ` Peter Korsgaard
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=5277415B.10202@mind.be \
--to=arnout@mind.be \
--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.