[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#891505: marked as done (glibc: Causes FTBFS of gcc-8 on hurd-i386)

Your message dated Mon, 29 Oct 2018 22:47:00 +0100
with message-id <20181029214700.ol7prqo5tof3vgxt@function>
and subject line Re: Bug#891505: glibc: Causes FTBFS of gcc-8 on hurd-i386
has caused the Debian Bug report #891505,
regarding glibc: Causes FTBFS of gcc-8 on hurd-i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
891505: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891505
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: glibc
Version: 2.26-6
Severity: important
Affects: gcc-8 glibc-2.26-*
User: debian-hurd@lists.debian.org
Usertags: hurd

Hi,

glibc versions > 2.25-6 breaks all builds of gcc-8-*/gccgo on GNU/Hurd due to
that -fdump-go-spec is broken.

>From the buildd logs of gcc-8:
8-20180218-1 (sid)          Maybe-Failed 2018-02-18 19:12:07
8-20180207-2 (sid)          Maybe-Failed 2018-02-07 23:22:42
8-20180130-1 (experimental) Maybe-Failed 2018-01-30 22:09:03
8-20180123-1 (experimental) Maybe-Failed 2018-01-24 08:22:30
8-20180110-1 (experimental) Maybe-Failed 2018-01-13 12:14:53
                            Maybe-Failed 2018-01-13 02:51:42
8-20171229-1 (experimental) Maybe-Successful 2018-01-02 03:39:06

Toolchain package versions: 2018-01-24
binutils_2.29.1-13 dpkg-dev_1.19.0.4 g++-7_7.2.0-19 gcc-7_7.2.0-19 gnumach-
dev_2:1.8+git20171101-1 hurd-dev_1:0.9.git20180108-1 libc0.3-dev_2.26-3
libstdc++-7-dev_7.2.0-19 libstdc++6_7.2.0-19
Toolchain package versions: 2018-01-02
binutils_2.29.1-12 dpkg-dev_1.19.0.4 g++-7_7.2.0-18 gcc-7_7.2.0-18 gnumach-
dev_2:1.8+git20171101-1 hurd-dev_1:0.9.git20171119-3 libc0.3-dev_2.25-6
libstdc++-7-dev_7.2.0-18 libstdc++6_7.2.0-18

The packages in the build environment was downgraded for the failing build and
the only package affecting the build was the libc version.

On gcc-8-8-20171229 the command:

/home/srs/DEBs/gcc-8/gcc-8-8-20171229/build/./gcc/xgcc -B/home/srs/DEBs/gcc-
8/gcc-8-8-20171229/build/./gcc/ -B/usr/i686-gnu/bin/ -B/usr/i686-gnu/lib/ 
-isystem /usr/i686-gnu/include -isystem /usr/i686-gnu/sys-include -isystem
/home/srs/DEBs/gcc-8/gcc-8-8-20171229/build/sys-include    -DHAVE_CONFIG_H -I. 
-I../../../src/libgo  -I ../../../src/libgo/runtime 
-I../../../src/libgo/../libffi/include -I../libffi/include -pthread  
-D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O 
-fdump-go-spec=tmp-gen-sysinfo.go -std=gnu99 -S -o sysinfo.s
../../../src/libgo/sysinfo.c
rm -f sysinfo.s
/bin/bash ../../../src/libgo/mvifdiff.sh tmp-gen-sysinfo.go gen-sysinfo.go

creates a defect gen-sysinfo.go file when libc0.3 >= 2.26-* is installed.

Attached is a diff of gen-sysinfo generated with glibc-2.26-6 and glibc-2.25-5
installed: (edited to show only a subset of the diff)

Thanks!
--- nOK/gen-sysinfo.go	2018-02-26 10:39:57.970054114 +0100
+++ OK/gen-sysinfo.go	2018-02-26 01:07:07.000000000 +0100
@@ -137,3 +137,4 @@
 // unknowndefine DT_WHT DT_WHT
 // unknowndefine SSIZE_MAX LONG_MAX
 // unknowndefine NULL ((void *)0)
+// unknowndefine EPERM _HURD_ERRNO (1)
...
+// unknowndefine ENOTRECOVERABLE _HURD_ERRNO (121)
 // unknowndefine errno (*__errno_location ())
 // unknowndefine O_READ O_RDONLY
 // unknowndefine O_WRITE O_WRONLY
@@ -156,6 +259,7 @@
 // unknowndefine SIG_DFL ((__sighandler_t) 0)
 // unknowndefine SIG_IGN ((__sighandler_t) 1)
 // unknowndefine SIG_HOLD ((__sighandler_t) 2)
+// unknowndefine SIGABRT SIGIOT
 // unknowndefine SI_ASYNCIO SI_ASYNCIO
 // unknowndefine SI_MESGQ SI_MESGQ
 // unknowndefine SI_TIMER SI_TIMER
@@ -196,6 +300,7 @@
 // unknowndefine POLL_ERR POLL_ERR
 // unknowndefine POLL_PRI POLL_PRI
 // unknowndefine POLL_HUP POLL_HUP
+// unknowndefine SIGEV_PAD_SIZE ((SIGEV_MAX_SIZE / sizeof (int)) - 3)
 // unknowndefine SIGEV_SIGNAL SIGEV_SIGNAL
 // unknowndefine SIGEV_NONE SIGEV_NONE
 // unknowndefine SIGEV_THREAD SIGEV_THREAD
@@ -211,8 +316,7 @@
 // unknowndefine NULL ((void *)0)
 // unknowndefine SS_ONSTACK SS_ONSTACK
 // unknowndefine SS_DISABLE SS_DISABLE
-// unknowndefine SIGRTMIN (__libc_current_sigrtmin ())
-// unknowndefine SIGRTMAX (__libc_current_sigrtmax ())// unknowndefine REG_GS REG_GS
+// unknowndefine REG_GS REG_GS
 // unknowndefine REG_FS REG_FS
 // unknowndefine REG_ES REG_ES
 // unknowndefine REG_DS REG_DS

--- End Message ---
--- Begin Message --- 
Samuel Thibault, le mar. 27 févr. 2018 10:38:15 +0100, a ecrit:
> Well, that can't be helped from the glibc side: EMIG_DESTROY_REQUEST
> etc. really are negative.  Please see with go people how that can be
> handled.

It was indeed fixed there since then.

Samuel

--- End Message ---
Reply to: