From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Supporting multiple versions of toolchain components?
Date: Wed, 12 Feb 2014 09:43:59 +0100 [thread overview]
Message-ID: <87mwhwu3e8.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20140212090324.4cb9fe84@skate> (Thomas Petazzoni's message of "Wed, 12 Feb 2014 09:03:24 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>> Note that I'm not immediately advocating for removing the multiple
>> version support where we have it already. Rather, I propose to not add
>> more multiversion packages.
> I certainly agree with you on this. I would propose to:
> 1/ Remove the multiversion selection on Busybox, because I don't
> really see why we have this specifically for Busybox.
> 2/ Keep a maximum number of three gcc, binutils, gdb and C library
> versions. Like: the latest one, the N-1 (default), and the N-2.
Sounds good to me. Let's also do the same for kernel headers. We still
need to keep the arch specific versions though.
Will you send patches or should I do it myself?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-02-12 8:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 17:43 [Buildroot] [PATCH] glibc: add 2.19 as a supported version Thomas Petazzoni
2014-02-10 20:29 ` Arnout Vandecappelle
2014-02-10 22:41 ` Thomas Petazzoni
2014-02-11 8:05 ` Arnout Vandecappelle
2014-02-11 8:19 ` Peter Korsgaard
2014-02-11 8:32 ` [Buildroot] Supporting multiple versions of toolchain components? Thomas Petazzoni
2014-02-11 17:16 ` Arnout Vandecappelle
2014-02-12 8:03 ` Thomas Petazzoni
2014-02-12 8:43 ` Peter Korsgaard [this message]
2014-02-12 17:37 ` Arnout Vandecappelle
2014-02-12 21:38 ` Thomas Petazzoni
2014-02-13 22:01 ` [Buildroot] [PATCH] glibc: add 2.19 as a supported version 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=87mwhwu3e8.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.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