New: glibc 2.20 and 2.21 fail to build for sh64-buildroot-linux-gnu

https://bugs.busybox.net/show_bug.cgi?id=7956

Host: x86_64
Target: sh64-buildroot-linux-gnu
Summary: glibc 2.20 and 2.21 fail to build for
sh64-buildroot-linux-gnu
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: uwe at hermann-uwe.de
CC: buildroot at uclibc.org
Estimated Hours: 0.0

This is with git HEAD as of today, glibc 2.20, gcc 4.9.x.

checking build system type... x86_64-unknown-linux-gnu
checking host system type... sh64-buildroot-linux-gnu
checking for sh64-buildroot-linux-gnu-gcc... /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-gcc checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-gcc accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C++ compiler... no
checking whether /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-g++ accepts -g... no
checking for sh64-buildroot-linux-gnu-readelf... /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-readelf checking for sysdeps preconfigure fragments... aarch64 alpha arm hppa i386 m68k
microblaze mips powerpc s390 sh sparc tile x86_64
configure: running configure fragment for add-on libidn
checking for assembler and linker STT_GNU_IFUNC support... no
checking whether .text pseudo-op must be used... yes
checking sysdep dirs... configure: error: The sh64 is not supported. package/pkg-generic.mk:172: recipe for target '/home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/build/glibc-2.20/.stamp_configured' failed
make: *** [/home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/build/glibc-2.20/.stamp_configured] Error 1

checking build system type... x86_64-unknown-linux-gnu
checking host system type... sh64-buildroot-linux-gnu
checking for sh64-buildroot-linux-gnu-gcc... /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-gcc checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-gcc accepts -g... yes
checking for gcc... gcc
checking whether we are using the GNU C++ compiler... no
checking whether /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-g++ accepts -g... no
checking for sh64-buildroot-linux-gnu-readelf... /home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/host/usr/bin/sh64-buildroot-linux-gnu-readelf checking for sysdeps preconfigure fragments... aarch64 alpha arm hppa i386 m68k
microblaze mips nios2 powerpc s390 sh sparc tile x86_64
configure: running configure fragment for add-on libidn
checking for assembler and linker STT_GNU_IFUNC support... no
checking whether .text pseudo-op must be used... yes
checking sysdep dirs... configure: error: The sh64 is not supported. package/pkg-generic.mk:172: recipe for target '/home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/build/glibc-2.21/.stamp_configured' failed
make: *** [/home/jenkins_slave/buildroot-sh64-buildroot-linux-gnu/output/build/glibc-2.21/.stamp_configured] Error 1

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=7956

--- Comment #1 from Thomas Petazzoni <[email protected]> 2015-04-09 13:03:59 UTC --- Do you actually use/need sh64 support? We're thinking of removing/deprecating
it.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=7956

--- Comment #2 from Uwe Hermann <[email protected]> 2015-04-09 16:01:34 UTC --- Well, I don't need it personally (at the moment), but we're trying to cross-compile our software (sigrok, open-source test&measurement project, see www.sigrok.org) for as many platforms as possible in order to catch any portability issues. We're using buildroot-built toolchains and sysroots for that since it's quite convenient.

See e.g.
http://sigrok.org/jenkins/job/libserialport/
http://sigrok.org/jenkins/job/libsigrok/

I don't know if we currently have users for sh64 or not, but that should not be relevant for this issue really.

I guess the question is whether mainline glibc supports sh64 at all or not. The text "configure: error: The sh64 is not supported." suggests the latter. But I didn't check whether that's actually true or an incorrect error is emitted (and/or whether sh64 support is planned to be added to glibc).

Note: I haven't tried the eglibc option for sh64 in buildroot, maybe that one does have support (?)

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

https://bugs.busybox.net/show_bug.cgi?id=7956

Thomas Petazzoni <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

--- Comment #3 from Thomas Petazzoni <[email protected]> 2015-06-03 01:08:36 UTC --- We've now marked sh64 as deprecated in Buildroot. According to the commit log:

sh64: deprecate support for this dead architecture

As discussed on the mailinglist, this should be deprecated before removal.

Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.