Bug#891505: glibc: Causes FTBFS of gcc-8 on hurd-i386
Svante Signell, on mar. 27 févr. 2018 10:26:35 +0100, wrote:
> 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?
Indeed.
> 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)
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.
Samuel
Reply to: