Running gas testsuite

[Stephen Casner]

On Mon, 18 May 2020, Alan Modra wrote:

> On Sun, May 17, 2020 at 05:48:55PM -0700, Stephen Casner wrote:
> > On Sun, 17 May 2020, Andrew Burgess wrote:
> >
> > > So maybe double check that your build tree is correctly configured to
> > > your source tree, and that your source tree doesn't have any missing
> > > files under gas/testsuite ?
> >
> > I figured out the true nature of the problem, and it may have to do
> > with how "correctly configured" is defined.
>
> You should be running the configure from the top source dir, ie. the
> dir containing bfd, opcodes, gas, ld and so on.

I _am_ running the configure that lives in the root binutils directory,
but you need to invoke it which connected to the build directory.  I
have been putting my build directory right below the binutils root
directory, so I have been configuring as:

    ../configure --target=xxx --prefix=xxx

That fails on

    make maybe-check-gas

Invoking configure with an absolute path instead does not fail.

You might say that using a relative pathname is bad practice.  I say
if that is the case, then configure should check and disallow it.  But
it is not necessary to impose that restriction, because the code in
the check-DEJAGNU rule could be more robust to tolerate the relative
pathname.

                                                        -- Steve