public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/98153] New: [11 Regression] libgo ftbfs on i686-gnu Date: Sat, 05 Dec 2020 09:24:29 +0000 [thread overview] Message-ID: <bug-98153-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98153 Bug ID: 98153 Summary: [11 Regression] libgo ftbfs on i686-gnu Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: go Assignee: ian at airs dot com Reporter: doko at debian dot org CC: cmang at google dot com Target Milestone: --- trunk 20201204 ftbfs on i686-gnu: ../../../src/libgo/go/syscall/socket_bsd.go:97:25: error: reference to undefined name 'AF_LINK' 97 | sa.raw.Family = AF_LINK | ^ Makefile:2957: recipe for target 'syscall.lo' failed make[6]: *** [syscall.lo] Error 1 make[6]: Leaving directory '/<<PKGBUILDDIR>>/build/i686-gnu/libgo' Makefile:2287: recipe for target 'all-recursive' failed make[5]: *** [all-recursive] Error 1
next reply other threads:[~2020-12-05 9:24 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-05 9:24 doko at debian dot org [this message] 2020-12-07 7:52 ` [Bug go/98153] " rguenth at gcc dot gnu.org 2020-12-07 22:06 ` svante.signell at gmail dot com 2020-12-07 22:11 ` svante.signell at gmail dot com 2020-12-08 1:08 ` cvs-commit at gcc dot gnu.org 2020-12-08 1:10 ` 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-98153-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).