i can't imagine this is a big runtime penalty, so why does configure check for
the perl's thread settings and then hardcode that in the generated automake ?
it means if you change your perl config or deploy an automake package on a
system that has threads disabled, you get errors when trying to
On 01/10/2013 08:57 PM, Timothée Flutre wrote:
> I updated M4, Autoconf and Automake to their latest version. In
> Makefile.am, I'm added only this:
>
> AM_TESTS_ENVIRONMENT = \
> myprog_abspath='$(abs_srcdir)'/../src/myprog; \
> export myprog_abspath;
>
> And now "make check" wor
I updated M4, Autoconf and Automake to their latest version. In
Makefile.am, I'm added only this:
AM_TESTS_ENVIRONMENT = \
myprog_abspath='$(abs_srcdir)'/../src/myprog; \
export myprog_abspath;
And now "make check" works! However, "make distcheck" doesn't. This is due
to the fact
On 01/09/2013 04:09 PM, Timothée Flutre wrote:
> Thanks, I've added TESTS_ENVIRONMENT (tried with or without "AC_")
>
(it's "AM_" BTW)
> in my test/Makefile.am and updated the rest like this:
>
> launch_functional_tests.bash: $(srcdir)/launch_functional_tests.in
> sed -e 's,PATHTOMYPROG,$
