From: "Lynn A. Boger" <laboger@linux.vnet.ibm.com>
To: 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: Mon, 08 Aug 2016 19:07:00 -0000 [thread overview]
Message-ID: <ecc75cec-52bd-cfff-3872-9d0e82b55365@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAOyqgcXsqE4fzBtEc-UdO5JcUnXamrFUg9-txg14vWGp4UAs5w@mail.gmail.com>
Sorry if I was unclear. Failures started happening with r239189, and it
continues to fail in the most recent commit, so none of the later
changes fixed the problem.
Only happens on trunk, ppc64le & ppc64 (m32 also). I did my build on a
different machine from the gcc-testresults build just to be sure there
wasn't something flaky with the system.
On 08/08/2016 01:26 PM, Ian Lance Taylor wrote:
> On Mon, Aug 8, 2016 at 11:14 AM, Lynn A. Boger
> <laboger@linux.vnet.ibm.com> wrote:
>> The libgo tests on ppc64le and ppc64 have all been failing in
>> gcc-testresults since this change went in and continues to fail after the
>> recent fixes for failures on other platforms.
>>
>> Built myself and got the same failures. I set keep=true in gotest to save
>> the test dirs. Just running a single package:
>>
>> make bufio/check
>> file /home/boger/gccgo.work/trunk/bld/../src/libgo/go/bufio/bufio.go not
>> found
>> Keeping gotest9734
>> FAIL: bufio
>> Makefile:3645: recipe for target 'bufio/check' failed
>> make: *** [bufio/check] Error 1
>> boger@willow3:~/gccgo.work/trunk/bld/powerpc64le-linux/libgo$ ls
>> /home/boger/gccgo.work/trunk/bld/../src/libgo/go/bufio/bufio.go
>> /home/boger/gccgo.work/trunk/bld/../src/libgo/go/bufio/bufio.go
>> boger@willow3:~/gccgo.work/trunk/bld/powerpc64le-linux/libgo$ file
>> /home/boger/gccgo.work/trunk/bld/../src/libgo/go/bufio/bufio.go
>> /home/boger/gccgo.work/trunk/bld/../src/libgo/go/bufio/bufio.go: ASCII text
> I do not know what would cause that and I'm not seeing it. I don't
> see how it could be related to the most recent patch (SVN revision
> 239225); was your build working before that patch and failing
> afterward?
>
> There is another report of the same problem on IRC so it's not just you.
>
> Ian
>
>
next prev parent reply other threads:[~2016-08-08 19:07 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
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 [this message]
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=ecc75cec-52bd-cfff-3872-9d0e82b55365@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 \
/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).