Am 09.02.2013 19:24, schrieb Ian Lance Taylor:
> On Sat, Feb 9, 2013 at 3:18 AM, Andreas Schwab <sch...@linux-m68k.org> wrote:
>> Ian Lance Taylor <i...@google.com> writes:
>>
>>> 2013-02-08 Ian Lance Taylor <i...@google.com>
>>>
>>> * lib/go.exp: Load timeout.exp.
>>
>> ERROR: Couldn't find library file timeout.exp.
>
> Sorry, I was told on IRC that the patch worked.
yes, it did work for me, but I only tested the default multilib location.
> As I mentioned on the bug, can you figure out why it fails? The file
> gcc/testsuite/lib/go.exp does a load_lib of several files from that
> directory. Why would they all work but loading timeout.exp fails?
but as I see now, it seems to fail for the non-default multilib locations. Is
there a somewhere a missing .. in a path?
the libgo testsuite unfortunately works not as all other testsuite for the
libraries do work. Usually if you do want to test a multilib build, you call
RUNTESTFLAGS="--target_board=unix\{,-m32,-mx32\}" make -k check
and only the check target for the default multilib is called. libgo however
descends into the non-default multilib targets and calls check there too. And
then with the above RUNTESTFLAGS, every go test is called nine times instead of
three times, and apparently fails the other six times.
Please let libgo behave the same as the other target libraries for the check
target, even it does introduce some delta.
Maybe this is seen on m68k too, because it's a multilib configuration too?
Matthias
