public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.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: Change build procedure to use build tags
Date: Sun, 04 Sep 2016 16:24:00 -0000	[thread overview]
Message-ID: <d0d57faf-e440-98cd-0fba-1b37054944d6@ubuntu.com> (raw)
In-Reply-To: <acc28e36-bc6e-5b4f-b9c5-7036cb8e8f7e@ubuntu.com>

On 07.08.2016 17:18, Matthias Klose wrote:
> On 07.08.2016 14:14, Andreas Schwab wrote:
>> That breaks ia64:
>>
>> ../../../libgo/go/internal/syscall/unix/getrandom_linux.go:29:5: error: reference to undefined name 'randomTrap'
>>   if randomTrap == 0 {
>>      ^
>> ../../../libgo/go/internal/syscall/unix/getrandom_linux.go:38:34: error: reference to undefined name 'randomTrap'
>>   r1, _, errno := syscall.Syscall(randomTrap,
>>                                   ^
>> make[4]: *** [internal/syscall/unix.lo] Error 1
> 
> same on s390x.

same on mips, mipsel, mips64el and sparc64.

Matthias

  parent reply	other threads:[~2016-09-04 14:51 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-06  0:36 Ian Lance Taylor
2016-08-07 12:14 ` Andreas Schwab
2016-08-07 15:18   ` Matthias Klose
2016-08-07 22:33     ` Ian Lance Taylor
2016-09-04 16:24     ` Matthias Klose [this message]
2016-09-23 21:53       ` Ian Lance Taylor
2016-08-08 18:15 ` Lynn A. Boger
2016-08-08 18:26   ` Ian Lance Taylor
2016-08-08 19:07     ` Lynn A. Boger
2016-08-08 20:34   ` Ian Lance Taylor
2016-08-09 15:46     ` Lynn A. Boger
2016-08-11 15:16 ` Rainer Orth
2016-08-11 21:36   ` Ian Lance Taylor
2016-08-12  9:15     ` Rainer Orth
2016-08-12 13:56       ` Rainer Orth
2016-08-13  2:53         ` Ian Lance Taylor
2016-08-13  0:14       ` Ian Lance Taylor
2016-08-12 11:20 ` Andreas Krebbel
2016-08-13  0:23   ` Ian Lance Taylor

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=d0d57faf-e440-98cd-0fba-1b37054944d6@ubuntu.com \
    --to=doko@ubuntu.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).