public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/67874] New: fd_unix.go does not build when there is fcntl64 and no fcntl syscall
Date: Tue, 06 Oct 2015 21:01:00 -0000	[thread overview]
Message-ID: <bug-67874-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 67874
           Summary: fd_unix.go does not build when there is fcntl64 and no
                    fcntl syscall
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: go
          Assignee: ian at airs dot com
          Reporter: pinskia at gcc dot gnu.org
                CC: cmang at google dot com
  Target Milestone: ---
            Target: aarch64-linux-gnu (ilp32)

Since a request from the ARM64 kernel maintainers on the ABI for AARCH64 ILP32
to just use off_t and time_t as 32bit rather than what I originally had it as
64bit, we use the compat syscalls instead which means there is no fcntl syscall
only fcntl64 now.

This breaks building fd_unix.go which depends on SYS_FCNTL being defined but
there is only SYS_FCNTL64 now.


             reply	other threads:[~2015-10-06 21:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 21:01 pinskia at gcc dot gnu.org [this message]
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
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@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).