Is testing libgomp outside of the build tree supported?

[Jakub Jelinek]

On Mon, Feb 03, 2014 at 11:11:31AM -0800, Ian Lance Taylor wrote:
> On Mon, Feb 3, 2014 at 10:03 AM, Paul Pluzhnikov <ppluzhnikov@google.com> wrote:
> >
> > We test GCC without access to the build tree (we only have convenient access to
> > install and source trees).
> >
> > Building libgomp.c/affinity-1.c and libgomp.c++/affinity-1.C fails in
> > such testing, because of '#include "config.h"' which is nowhere to be
> > found.
> >
> > Is that a bug?
> > Should I open a bugzilla issue for it?
> 
> If it's easy to fix then I think it should be fixed.
> 
> But I don't think there should be a hard and fast rule that all GCC
> tests can be run without the build tree.  If the presence of the build
> tree makes writing some tests significantly simpler, I think that is
> OK.

If there is some effective target or similar way to limit the tests to
build tree testing, then those tests probably could be guarded by that,
otherwise you'll have to live with the FAILs, there isn't an easy way to
reconstruct the configure tests whether it is ok to use the affinity or not.

	Jakub