public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: Andreas Schwab <schwab@linux-m68k.org>,
	Ian Lance Taylor <iant@golang.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
	       "gofrontend-dev@googlegroups.com"
	<gofrontend-dev@googlegroups.com>
Subject: Re: libgo patch committed: Update to Go 1.5 release
Date: Mon, 02 Nov 2015 15:40:00 -0000	[thread overview]
Message-ID: <563783C7.5050505@linux.vnet.ibm.com> (raw)
In-Reply-To: <mvmfv0obv2q.fsf@hawking.suse.de>

I see this error when building gccgo from trunk on ppc64le and running 
the libgo tests:

exec_unix_test.go:174:43: error: reference to undefined identifier 
'syscall.TIOCGPGRP'
   errno := syscall.Ioctl(tty.Fd(), syscall.TIOCGPGRP, 
uintptr(unsafe.Pointer(&fpgrp)))
                                            ^
FAIL: syscall
make[3]: *** [syscall/check] Error 1


On 11/02/2015 03:37 AM, Andreas Schwab wrote:
> Ian Lance Taylor <iant@golang.org> writes:
>
>> On Sun, Nov 1, 2015 at 1:39 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>>> ../../../../libgo/go/syscall/exec_linux.go:185:37: error: reference to undefined name 'TIOCSPGRP'
>>>     _, err1 = raw_ioctl_ptr(sys.Ctty, TIOCSPGRP, unsafe.Pointer(&pgrp))
>>>                                       ^
>>>
>>> $ grep TIOCSPGRP gen-sysinfo.go
>>> // unknowndefine TIOCSPGRP _IOW('t', 118, int)
>> I have committed this patch which may fix the problem.  Let me know if
>> it still happens for you.  Thanks.
> ../../../../libgo/go/syscall/exec_linux.go:185:37: error: integer constant overflow
>     _, err1 = raw_ioctl_ptr(sys.Ctty, TIOCSPGRP, unsafe.Pointer(&pgrp))
>
> // unknowndefine TIOCSPGRP _IOW('t', 118, int)
> const _TIOCSPGRP_val = 2147775606
>
> Andreas.
>

  reply	other threads:[~2015-11-02 15:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-31  3:35 Ian Lance Taylor
2015-11-01  8:40 ` Andreas Schwab
2015-11-01 20:33   ` Ian Lance Taylor
2015-11-01 20:52   ` Ian Lance Taylor
2015-11-02  9:38     ` Andreas Schwab
2015-11-02 15:40       ` Lynn A. Boger [this message]
2015-11-02 20:23         ` Ian Lance Taylor
2015-11-02 20:59           ` Lynn A. Boger
2015-11-02 23:30             ` [gofrontend-dev] " Ian Lance Taylor
2015-11-02 19:58       ` Ian Lance Taylor
2015-11-06 13:01 ` Rainer Orth
2015-11-06 19:16   ` Ian Lance Taylor
2015-11-08 17:21     ` Rainer Orth
2015-11-10 21:39       ` Ian Lance Taylor
2015-11-11 11:48         ` Rainer Orth
2015-11-11 13:25           ` Ian Lance Taylor
2015-11-03  7:48 Uros Bizjak
2015-11-03 15:07 ` Ian Lance Taylor
2015-11-03 15:48   ` Lynn A. Boger
2015-11-03 17:34     ` Ian Lance Taylor
2015-11-03 20:17       ` Lynn A. Boger
2015-11-04  1:53         ` Ian Lance Taylor
2015-11-03 22:14       ` Andreas Schwab

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=563783C7.5050505@linux.vnet.ibm.com \
    --to=laboger@linux.vnet.ibm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=iant@golang.org \
    --cc=schwab@linux-m68k.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).