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/104290] New: [12 Regression] trunk 20220126 fails to build libgo on i686-gnu
Date: Sun, 30 Jan 2022 13:38:49 +0000 [thread overview]
Message-ID: <bug-104290-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104290
Bug ID: 104290
Summary: [12 Regression] trunk 20220126 fails to build libgo on
i686-gnu
Product: gcc
Version: 12.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 20220126 fails to build libgo on i686-gnu:
../../../src/libgo/go/net/unixsock_posix.go:116:56: error: reference to
undefined name 'readMsgFlags'
116 | n, oobn, flags, sa, err = c.fd.readMsg(b, oob, readMsgFlags)
| ^
../../../src/libgo/go/net/unixsock_posix.go:117:12: error: reference to
undefined name 'readMsgFlags'
117 | if readMsgFlags == 0 && err == nil && oobn > 0 {
| ^
../../../src/libgo/go/net/unixsock_posix.go:118:17: error: reference to
undefined name 'setReadMsgCloseOnExec'
118 | setReadMsgCloseOnExec(oob[:oobn])
| ^
Makefile:3026: recipe for target 'net.lo' failed
make[6]: *** [net.lo] Error 1
next reply other threads:[~2022-01-30 13:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-30 13:38 doko at debian dot org [this message]
2022-01-31 8:21 ` [Bug go/104290] " rguenth at gcc dot gnu.org
2022-02-03 15:16 ` svante.signell at gmail dot com
2022-02-06 11:43 ` svante.signell at gmail dot com
2022-02-08 17:08 ` svante.signell at gmail dot com
2022-02-08 17:29 ` schwab@linux-m68k.org
2022-02-08 17:50 ` ian at airs dot com
2022-02-08 19:37 ` svante.signell at gmail dot com
2022-02-08 19:44 ` schwab@linux-m68k.org
2022-02-09 22:11 ` svante.signell at gmail dot com
2022-02-17 17:30 ` cvs-commit at gcc dot gnu.org
2022-02-17 22:20 ` svante.signell at gmail dot com
2022-02-17 22:21 ` svante.signell at gmail dot com
2022-02-17 22:22 ` svante.signell at gmail dot com
2022-02-17 22:23 ` svante.signell at gmail dot com
2022-02-17 22:23 ` svante.signell at gmail dot com
2022-02-17 22:24 ` svante.signell at gmail dot com
2022-02-17 22:25 ` svante.signell at gmail dot com
2022-02-17 22:25 ` svante.signell at gmail dot com
2022-02-17 22:26 ` svante.signell at gmail dot com
2022-02-17 22:41 ` svante.signell at gmail dot com
2022-02-17 22:45 ` svante.signell at gmail dot com
2022-02-18 18:28 ` ian at airs dot com
2022-02-18 22:57 ` ian at airs dot com
2022-02-18 23:33 ` [Bug go/104290] [12 Regression] trunk 20220214 " cvs-commit at gcc dot gnu.org
2022-02-19 9:40 ` svante.signell at gmail dot com
2022-02-20 20:15 ` ian at airs dot com
2022-02-21 16:05 ` svante.signell at gmail dot com
2022-02-21 16:23 ` ian at airs dot com
2022-05-06 8:32 ` [Bug go/104290] [12/13 " jakub at gcc dot gnu.org
2022-07-26 13:01 ` rguenth at gcc dot gnu.org
2022-07-29 6:31 ` pinskia at gcc dot gnu.org
2023-02-21 14:59 ` rguenth at gcc dot gnu.org
2023-02-21 17:00 ` ian at airs dot com
2023-03-15 16:27 ` svante.signell at gmail dot com
2023-05-08 12:23 ` [Bug go/104290] [12/13/14 " rguenth 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-104290-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).