public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/106266] New: Libgo fails with recent glibc Date: Tue, 12 Jul 2022 07:21:53 +0000 [thread overview] Message-ID: <bug-106266-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106266 Bug ID: 106266 Summary: Libgo fails with recent glibc Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: marxin at gcc dot gnu.org Target Milestone: --- Fails with: [ 4342s] /home/abuild/rpmbuild/BUILD/gcc-13.0.0+git194331/obj-x86_64-suse-linux/./gcc/xgcc -B/home/abuild/rpmbuild/BUILD/gcc-13.0.0+git194331/obj-x86_64-suse-linux/./gcc/ -B/usr/x86_64-suse-linux/bin/ -B/usr/x86_64-suse-linux/lib/ -isystem /usr/x86_64-suse-linux/include -isystem /usr/x86_64-suse-linux/sys-include -DHAVE_CONFIG_H -I. -I../../../libgo -I ../../../libgo/runtime -I../../../libgo/../libffi/include -I../libffi/include -pthread -L../libatomic/.libs -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 ../../../libgo/sysinfo.c [ 4342s] In file included from /usr/include/linux/fs.h:19, [ 4342s] from ../../../libgo/sysinfo.c:162: [ 4342s] /usr/include/linux/mount.h:95:6: error: redeclaration of 'enum fsconfig_command' [ 4342s] 95 | enum fsconfig_command { [ 4342s] | ^~~~~~~~~~~~~~~~ [ 4342s] In file included from ../../../libgo/sysinfo.c:141: [ 4342s] /usr/include/sys/mount.h:189:6: note: originally defined here [ 4342s] 189 | enum fsconfig_command [ 4342s] | ^~~~~~~~~~~~~~~~ It's very similar to the following libsanitizer issue: https://github.com/llvm/llvm-project/issues/56421
next reply other threads:[~2022-07-12 7:21 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-12 7:21 marxin at gcc dot gnu.org [this message] 2022-07-12 7:22 ` [Bug go/106266] " marxin at gcc dot gnu.org 2022-07-13 16:02 ` cvs-commit at gcc dot gnu.org 2022-07-13 16:03 ` ian at airs dot com 2022-07-21 11:53 ` cvs-commit at gcc dot gnu.org 2022-07-21 11:59 ` cvs-commit at gcc dot gnu.org 2022-07-21 12:09 ` cvs-commit at gcc dot gnu.org
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-106266-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: linkBe 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).