public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/99458] New: libgo doesn't build against latest glibc
Date: Mon, 08 Mar 2021 09:16:02 +0000 [thread overview]
Message-ID: <bug-99458-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99458
Bug ID: 99458
Summary: libgo doesn't build against latest glibc
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: jakub at gcc dot gnu.org
CC: cmang at google dot com
Target Milestone: ---
As mentioned already in PR99264 which is now fixed, latest glibc changed the
MINSIGSTKSZ and SIGSTKSZ macros so that they are no longer compile time
constants.
This seems to break libgo build (got that when building the 32-bit libgo on
x86_64 e.g.):
../../../../libgo/runtime/proc.c: In function 'runtime_malg':
../../../../libgo/runtime/proc.c:805:38: error: comparison of integer
expressions of different signedness: 'uintptr' {aka 'unsigned int'} and 'long
int' [-Werror=sign-compare]
805 | if(stacksize < SIGSTKSZ)
| ^
Guess SIGSTKSZ should be cast to (uintptr).
next reply other threads:[~2021-03-08 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 9:16 jakub at gcc dot gnu.org [this message]
2021-03-08 9:23 ` [Bug go/99458] " marxin at gcc dot gnu.org
2021-03-09 0:16 ` cvs-commit at gcc dot gnu.org
2021-03-09 0:17 ` cvs-commit at gcc dot gnu.org
2021-03-09 0:23 ` cvs-commit at gcc dot gnu.org
2021-03-09 0:24 ` ian at airs dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-99458-4@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).