public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/106266] Libgo fails with recent glibc
Date: Thu, 21 Jul 2022 11:53:16 +0000	[thread overview]
Message-ID: <bug-106266-4-fasQCSjxVd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106266-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106266

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-12 branch has been updated by Martin Liska
<marxin@gcc.gnu.org>:

https://gcc.gnu.org/g:4f15d2234608e82159d030dadb17af678cfad626

commit r12-8599-g4f15d2234608e82159d030dadb17af678cfad626
Author: Ian Lance Taylor <iant@golang.org>
Date:   Tue Jul 12 19:42:43 2022 -0700

    libgo: don't include <linux/fs.h> when building gen-sysinfo.go

    Removing this doesn't change anything at least with glibc 2.33.
    The include was added in https://go.dev/cl/6100049 but it's not
    clear why.

    Fixes PR go/106266

    Reviewed-on: https://go-review.googlesource.com/c/gofrontend/+/417294
    (cherry picked from commit f35d65517a59565758107c5b1a51a5fa382f8d1a)

  parent reply	other threads:[~2022-07-21 11:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-12  7:21 [Bug go/106266] New: " marxin at gcc dot gnu.org
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 [this message]
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-fasQCSjxVd@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).