public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug go/67874] fd_unix.go does not build when there is fcntl64 and no fcntl syscall Date: Wed, 07 Oct 2015 17:22:00 -0000 [thread overview] Message-ID: <bug-67874-4-36GN0qGTl0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67874-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67874 --- Comment #2 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> --- Author: ian Date: Wed Oct 7 17:22:08 2015 New Revision: 228576 URL: https://gcc.gnu.org/viewcvs?rev=228576&root=gcc&view=rev Log: PR go/67874 net, runtime: Call C library fcntl function rather than syscall.Syscall. Not all systems define a fcntl syscall; some only have fcntl64. Fixes GCC PR go/67874. Reviewed-on: https://go-review.googlesource.com/15497 Modified: trunk/gcc/go/gofrontend/MERGE trunk/libgo/go/net/fd_unix.go trunk/libgo/runtime/go-varargs.c
next prev parent reply other threads:[~2015-10-07 17:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-06 21:01 [Bug go/67874] New: " pinskia at gcc dot gnu.org 2015-10-06 21:03 ` [Bug go/67874] " pinskia at gcc dot gnu.org 2015-10-07 17:22 ` ian at gcc dot gnu.org [this message] 2015-10-07 17:28 ` 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-67874-4-36GN0qGTl0@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).