On 07/12/17 15:17, Joseph Myers wrote:
On Thu, 7 Dec 2017, Thomas Preudhomme wrote:
That seems to go counter to the --prefix option of contrib/test_installed
which is meant to test a compiler at an arbitrary path. This suggest the
compiler is not expected to be in PATH or in any dejagnu configu
On Thu, 7 Dec 2017, Thomas Preudhomme wrote:
> That seems to go counter to the --prefix option of contrib/test_installed
> which is meant to test a compiler at an arbitrary path. This suggest the
> compiler is not expected to be in PATH or in any dejagnu configuration file.
> Seems most of the tes
Hi Joseph,
On 06/12/17 17:53, Joseph Myers wrote:
On Wed, 6 Dec 2017, Thomas Preudhomme wrote:
== problem ==
I'm not sure where is the proper place to fix this. Obviously setting
CC_FOR_TARGET in contrib/test_installed or when calling runtest manually would
work but I wonder if this would not
On Wed, 6 Dec 2017, Thomas Preudhomme wrote:
> == problem ==
>
> I'm not sure where is the proper place to fix this. Obviously setting
> CC_FOR_TARGET in contrib/test_installed or when calling runtest manually would
> work but I wonder if this would not be better fixed somewhere else? The rest
>
Hi,
TL;DR: where to tell dejagnu about the compiler to use for building testglue?
== context ==
I've just found out that testglue.c is built using the compiler in PATH when
doing out of tree testing rather than using the one specified by GCC_UNDER_TEST
(or other *_UNDER_TEST). This is because
