public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@golang.org>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
		"gofrontend-dev@googlegroups.com"
	<gofrontend-dev@googlegroups.com>
Subject: Re: Top-level patch committed: Add check-gotools to check-go
Date: Fri, 16 Jun 2017 00:12:00 -0000	[thread overview]
Message-ID: <CAOyqgcXo8ZYW-x+Q+vQiWg6NEMQaBKFK6gCMpxTjjTPukpox1A@mail.gmail.com> (raw)
In-Reply-To: <yddfuf155l0.fsf@CeBiTec.Uni-Bielefeld.DE>

On Thu, Jun 15, 2017 at 2:00 PM, Rainer Orth
<ro@cebitec.uni-bielefeld.de> wrote:
>
>> I've committed this patch to the top level Makefile.def so that `make
>> check-go` will run `make check-gotools`.  Bootstrapped and ran Go
>> testsuite on x86_64-pc-linux-gnu.  Committed to mainline.
>>
>> This patch may cause new test failures on other systems.  Please let
>> me know about them.  I don't anticipate anything in particular, but,
>> who knows.
>
> the gotools test results came up empty on *-*-solaris2.12 with /bin/ksh.
> In the make check-gotools output I found
>
> (cd check-go-dir/src/cmd/go && /var/gcc/regression/trunk/12-gcc/build/gotools/go test -test.short -test.v) >& cmd_go-testlog || true
> /bin/ksh: line 3: cmd_go-testlog: bad file unit number
>
> If one uses the portable form of I/O redirection here, the test works on
> Solaris, too.
>
>         Rainer
>
> --
> -----------------------------------------------------------------------------
> Rainer Orth, Center for Biotechnology, Bielefeld University
>
>
> 2017-06-15  Rainer Orth  <ro@CeBiTec.Uni-Bielefeld.DE>
>
>         * Makefile.am (check-go-tool): Don't use >& for I/O redirection.
>         * Makefile.in: Regenerate.

Whoops.

This is OK.  You can go ahead and commit--unlike the go/gofrontend and
libgo directories, this directory lives entirely in the GCC tree.

Thanks.

Ian

      reply	other threads:[~2017-06-16  0:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-14 19:36 Ian Lance Taylor
2017-06-15 21:01 ` Rainer Orth
2017-06-16  0:12   ` Ian Lance Taylor [this message]

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=CAOyqgcXo8ZYW-x+Q+vQiWg6NEMQaBKFK6gCMpxTjjTPukpox1A@mail.gmail.com \
    --to=iant@golang.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gofrontend-dev@googlegroups.com \
    --cc=ro@cebitec.uni-bielefeld.de \
    /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).