Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Reduce toolchain options
Date: Wed, 11 Mar 2015 23:04:19 +0100	[thread overview]
Message-ID: <5500BBE3.2030709@mind.be> (raw)
In-Reply-To: <550069E9.5060403@zacarias.com.ar>

On 11/03/15 17:14, Gustavo Zacarias wrote:
> 
> Hi.
> How about we kill non-lfs and non-ipv6 toolchains?

 Sounds like a good idea!

> 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

 Could you calculate this with STATIC and thumb and also report the baseline?
IIRC a minimal statically linked busybox was only about 200K so the 20K
largefile is borderline significant...


 Regards,
 Arnout

> 
> 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.
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
> 
> 


-- 
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

  parent reply	other threads:[~2015-03-11 22:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:14 [Buildroot] Reduce toolchain options Gustavo Zacarias
2015-03-11 16:28 ` 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 [this message]
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=5500BBE3.2030709@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox