sorry to self-followup. * Ralf Wildenhues wrote on Sat, Apr 16, 2005 at 05:59:17PM CEST: > * Peter O'Gorman wrote on Sat, Apr 16, 2005 at 05:30:01PM CEST: > > Peter O'Gorman wrote: > > Hmm. Maybe we should consider using > eval `$LIBTOOL --config | grep EGREP=` > eval `$LIBTOOL --config | $EGREP '(host|build)=` > when lines like these start to accumulate. (Just thinking out loud.)
Adding EGREP to TESTS_ENVIRONMENT would be even better.. > > +if test "X$host" != "X$build"; then > > + AT_CHECK([test -x ./main],[0],[ignore],[ignore]) > The `test -x' is ok, but even when cross-compiling, I would like that we > try to execute it, but just not fail if it doesn't work. Reason is that > you might want to cross-compile for, say, older versions of your system > (i686 -> i486). No strong opinion, though, except it'd be nice if we > did it consistently. > > Other than that, you certainly don't want to ignore the output here. Another reason it's wrong: `test -x ./main' ignores EXEEXT. Cygwin works around it fine, but it fails when cross-compiling linux -> cygwin. (I just stumbled over a similar issue in a test.) Regards, Ralf
