From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Tue, 1 May 2018 21:19:12 +0200 Subject: [Buildroot] [PATCH] DEVELOPERS: concentrate on uClibc In-Reply-To: <20180501174118.GE31635@waldemar-brodkorb.de> References: <20180428203511.GA24621@waldemar-brodkorb.de> <20180428225858.0cd63f20@windsurf> <20180501174118.GE31635@waldemar-brodkorb.de> Message-ID: <20180501211912.687fce24@windsurf.home> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Tue, 1 May 2018 19:41:18 +0200, Waldemar Brodkorb wrote: > > I understand the wish to concentrate on a smaller number of topics. > > However, who is going to take care of the m68k, sparc and OpenRISC > > architecture in Buildroot? I think besides you, not many people were > > interested by those architectures, and they cause fairly frequent > > issues at the toolchain level. Do you have a proposal here ? > > I keep responding on the build failure summary mails before a > release. The normal buildroot mails are more informative for me > then the summary for the architectures I subscribed. There I can see > if it is really specific architecture issue or the failure shows up on many > others. Indeed, makes sense. > And I am always interested in other uClibc-ng toolchain > related issues on other exotic architectures. (microblaze, nios2, ..) Great, thanks! Thomas -- Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons) Embedded Linux and Kernel engineering https://bootlin.com