All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] Reduce toolchain options
Date: Wed, 11 Mar 2015 13:14:33 -0300	[thread overview]
Message-ID: <550069E9.5060403@zacarias.com.ar> (raw)


Hi.
How about we kill non-lfs and non-ipv6 toolchains?
It's 2015 after all, and the size delta is minor:

tar file delta, arm926 uclibc+busybox
=====================================
Threading (NPTL)        +153600 bytes
Largefile               +20480 bytes
IPv6                    +10240 bytes
RPC                     +61440 bytes
WCHAR                   +30720 bytes

Benefits:
* Less toolchain options to test/care for in packages
* More bang for the buck for autobuilders with less combinations to test

Even though the size delta would be somewhat more (tiny though) when
adding packages/libraries that's generally offset by the added size of
said packages.

The only downside i can think of is badly designed packages that won't
work well on a non-ipv6 linux kernel. These should be very few, if any.

LFS is a no brainer IMO.

Regards.

             reply	other threads:[~2015-03-11 16:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:14 Gustavo Zacarias [this message]
2015-03-11 16:28 ` [Buildroot] Reduce toolchain options Peter Korsgaard
2015-03-11 18:27   ` Gustavo Zacarias
2015-03-11 20:23     ` Peter Korsgaard
2015-03-11 20:44     ` Thomas Petazzoni
2015-03-11 21:43       ` Gustavo Zacarias
2015-03-11 20:45 ` Thomas Petazzoni
2015-03-11 21:40   ` Peter Korsgaard
2015-03-11 21:45     ` Gustavo Zacarias
2015-03-11 21:42   ` Gustavo Zacarias
2015-03-11 22:04 ` Arnout Vandecappelle
2015-03-11 23:02   ` 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=550069E9.5060403@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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.