Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-28 Thread John David Anglin
On 2017-11-28 9:47 AM, James Clarke wrote: [Cc'ing hppa people for reasons which will become clear] On Tue, Nov 28, 2017 at 08:22:56AM -0500, Jason Duerstock wrote: Source: glibc Followup-For: Bug #882874 This patch appears to correct the problem. -- System Information: Debian Release:

Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-28 Thread James Clarke
[Cc'ing hppa people for reasons which will become clear] On Tue, Nov 28, 2017 at 08:22:56AM -0500, Jason Duerstock wrote: > Source: glibc > Followup-For: Bug #882874 > > This patch appears to correct the problem. > > -- System Information: > Debian Release: buster/sid > Architecture: ia64 > >

Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-28 Thread Jason Duerstock
Source: glibc Followup-For: Bug #882874 This patch appears to correct the problem. -- System Information: Debian Release: buster/sid Architecture: ia64 Kernel: Linux 3.2.0-4-mckinley (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to

Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-27 Thread Jason Duerstock
I understand. Thank you. On Mon, Nov 27, 2017 at 3:23 PM, Aurelien Jarno wrote: > Hi, > > On 2017-11-27 13:08, Jason Duerstock wrote: > > Source: glibc > > Version: 2.25 > > Severity: normal > > > > Dear Maintainer, > > When trying to build glibc 2.25 under ia64, ld.so

Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-27 Thread Aurelien Jarno
Hi, On 2017-11-27 13:08, Jason Duerstock wrote: > Source: glibc > Version: 2.25 > Severity: normal > > Dear Maintainer, > When trying to build glibc 2.25 under ia64, ld.so does not build properly, > and produces a segmentation fault immediately upon execution. Just to be clear, Debian doesn't

Bug#882874: glibc 2.25 FTBFS on ia64

2017-11-27 Thread Jason Duerstock
Source: glibc Version: 2.25 Severity: normal Dear Maintainer, When trying to build glibc 2.25 under ia64, ld.so does not build properly, and produces a segmentation fault immediately upon execution. The following backtrace is common to every combination of toolchain part and compilation flag