DEVELOPERS: concentrate on uClibc

Signed-off-by Waldemar Brodkorb <[email protected]>

---
 DEVELOPERS | 5 -----
 1 file changed, 5 deletions(-)

DEVELOPERS +0 -0

index 3a4ad60..45a8979 100644

Hello,

Quoted 12 lines · Waldemar Brodkorb

Signed-off-by Waldemar Brodkorb <[email protected]>

---
 DEVELOPERS | 5 -----
 1 file changed, 5 deletions(-)

DEVELOPERS +0 -0

index 3a4ad60..45a8979 100644
@@ -1952,11 +1952,6 @@ N:	Wade Berrier <[email protected]>
 F:	package/ngrep/
 

DEVELOPERS N: Wade Berrier <[email protected]> · line 1956

Quoted 8 lines

DEVELOPERS +0 -5

 N:	Waldemar Brodkorb <[email protected]>
-F:	arch/Config.in.m68k
-F:	arch/Config.in.or1k
-F:	arch/Config.in.sparc
-F:	package/glibc/
-F:	package/mksh/
 F:	package/uclibc/
 F:	package/uclibc-ng-test/

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 ?

Quoted 5 lines

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.

And I am always interested in other uClibc-ng toolchain related issues on other exotic architectures. (microblaze, nios2, ..)

Signed-off-by Waldemar Brodkorb <[email protected]>

---
 DEVELOPERS | 5 -----
 1 file changed, 5 deletions(-)