From: Waldemar Brodkorb <wbx@openadk.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file.
Date: Tue, 18 Jul 2017 23:07:04 +0200 [thread overview]
Message-ID: <20170718210704.GO1482@waldemar-brodkorb.de> (raw)
In-Reply-To: <20170718230641.479308e9@windsurf>
Hi,
Thomas Petazzoni wrote,
> Hello,
>
> On Tue, 18 Jul 2017 21:24:05 +0200, Arnout Vandecappelle wrote:
>
> > I'm with you on this one. If a package can work with uClibc, we really should
> > allow it.
> >
> > However, I don't think the solution is to bloat our default uClibc config with
> > features that are not useful for 99.82% of our packages. fts.h is not something
> > like IPv6 that is useful for a large number of packages.
> >
> > I also don't think we should add more options like BR2_ENABLE_LOCALE that copy
> > the uClibc config options.
> >
> > Perhaps the way to go is to have a BR2_TOOLCHAIN_UCLIBC_BLOAT_CONFIG option
> > that a user can set to indicate he wants to see packages that will not work with
> > our default uClibc config. That option could give a nice warning that this
> > configuration is not tested and YMMV.
>
> I have to say I don't like this. If we have an option, it should work,
> and therefore be tested. It's the worst thing for users to simply tick
> an option, and discover build failures here and there. If you have an
> option that explicitly allows to do something, then that something
> should work.
I still don't get it.
We are not trying to disable fts in glibc, so it is available there.
Why we can't enable it for uClibc-ng to get more compatibility?
Just because of the bigger size?
If someone needs a really small system, there is always the
possibilty to use a really small uClibc-ng config.
best regards
Waldemar
next prev parent reply other threads:[~2017-07-18 21:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 14:25 [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file Adam Duskett
2017-07-13 14:25 ` [Buildroot] [PATCH 2/2] selinux packages: change glibc check to musl check Adam Duskett
2017-07-13 17:32 ` [Buildroot] [PATCH 1/2] uclibc-ng: enable fts in default config file Thomas Petazzoni
2017-07-13 17:41 ` Adam Duskett
2017-07-15 9:44 ` Thomas Petazzoni
2017-07-15 15:15 ` Peter Korsgaard
2017-07-15 17:16 ` Adam Duskett
2017-07-15 19:48 ` Thomas Petazzoni
2017-07-15 20:09 ` Adam Duskett
2017-07-16 15:53 ` Peter Korsgaard
2017-07-16 16:43 ` Waldemar Brodkorb
2017-07-16 17:40 ` Adam Duskett
2017-07-16 18:46 ` Yann E. MORIN
2017-07-18 19:24 ` Arnout Vandecappelle
2017-07-18 21:06 ` Thomas Petazzoni
2017-07-18 21:07 ` Waldemar Brodkorb [this message]
2017-10-12 1:06 ` Alexey Brodkin
2017-10-12 7:52 ` Thomas Petazzoni
2017-10-12 18:08 ` Waldemar Brodkorb
2017-10-12 18:56 ` ratbert90
2017-10-13 16:59 ` Alexey Brodkin
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=20170718210704.GO1482@waldemar-brodkorb.de \
--to=wbx@openadk.org \
--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