Bug#891505: glibc: Causes FTBFS of gcc-8 on hurd-i386
On Mon, 2018-02-26 at 23:55 +0100, Samuel Thibault wrote:
> Svante Signell, on lun. 26 févr. 2018 11:22:22 +0100, wrote:
> > creates a defect gen-sysinfo.go file when libc0.3 >= 2.26-* is installed.
>
> A lot of cleanup has happened, yes. The question is what actually made
> gcc-8 to break. Just looking at the diff of the build logs, there's
>
> could not determine number of signals
...
> To confirm this hypothesis, you could modify your
> /usr/include/i386-gnu/bits/signum-generic.h
> from
> #define _NSIG (__SIGRTMAX + 1)
> to
> #define _NSIG 32
You mean 33, right?
With that change the number of signals are correctly calculated. However, there
are still problems with the negative values of _EMIG_* error for Errno()
sysinfo.go:3399:35: error: integer constant overflow
const EMIG_DESTROY_REQUEST = Errno(_EMIG_DESTROY_REQUEST)
^
sysinfo.go:3413:26: error: integer constant overflow
const EMIG_BAD_ID = Errno(_EMIG_BAD_ID)
^
sysinfo.go:3414:31: error: integer constant overflow
const EMIG_SERVER_DIED = Errno(_EMIG_SERVER_DIED)
^
sysinfo.go:3425:32: error: integer constant overflow
const EMIG_REMOTE_ERROR = Errno(_EMIG_REMOTE_ERROR)
^
sysinfo.go:3429:30: error: integer constant overflow
const EMIG_TYPE_ERROR = Errno(_EMIG_TYPE_ERROR)
^
sysinfo.go:3460:28: error: integer constant overflow
const EMIG_NO_REPLY = Errno(_EMIG_NO_REPLY)
^
sysinfo.go:3473:34: error: integer constant overflow
const EMIG_REPLY_MISMATCH = Errno(_EMIG_REPLY_MISMATCH)
^
sysinfo.go:3475:33: error: integer constant overflow
const EMIG_BAD_ARGUMENTS = Errno(_EMIG_BAD_ARGUMENTS)
^
sysinfo.go:3540:29: error: integer constant overflow
const EMIG_EXCEPTION = Errno(_EMIG_EXCEPTION)
^
sysinfo.go:3564:35: error: integer constant overflow
const EMIG_ARRAY_TOO_LARGE = Errno(_EMIG_ARRAY_TOO_LARGE)
Reply to: