On Mon, Feb 18, 2013 at 12:23 AM, Matthias Klose <d...@ubuntu.com> wrote:
>
>> 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?
I thought this was fixed now by a patch to
libgo/testsuite/lib/libgo.exp. Are you still seeing trouble with
current mainline?
> 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.
I can't remember if there is a bug report open for this or not.
Ian
