run_tests.sh fail when running configure script with absolute path

[jaydee-io]

When running the configure script with an absolute path, run_tests.sh fail.
See output.txt and test-suite.log for details.

$ tar -xf /tmp/packages/re2c-0.16.tar.gz -C /tmp/sources/re2c-0.16 --strip-components 1
$ cd /tmp/build/re2c-0.16
$ /tmp/sources/re2c-0.16/configure --prefix=/tmp/install --enable-docs
$ make -j8 bootstrap docs
$ make -j8 check

The same using a relative path leads to run_tests.sh success.

$ tar -xf /tmp/packages/re2c-0.16.tar.gz -C /tmp/sources/re2c-0.16 --strip-components 1
$ cd /tmp/build/re2c-0.16
$ ../../sources/re2c-0.16/configure --prefix=/tmp/install --enable-docs
$ make -j8 bootstrap docs
$ make -j8 check

[skvadrik]

Confirmed, thanks for reporting.
Yet I'm not sure what is the simplest portable way to tell if a path is absolute/relative in bash.

[jaydee-io]

I'm currently working to submit you a patch of run_tests.sh using readlink -f to convert to absolute path.

But first, I'm not sure if it's portable to Wine.
And under Mac OS X the default readline command doesn't support -foption. We need to use greadlink instead.

brew install coreutils
greadlink -f file.txt

[skvadrik]

Sadly, readlink is also non-POSIX (thanks for your effort anyway).

I think I've come up with a more portable fix: simply copy all test sources to test_blddir and keep using relative paths.

[jaydee-io]

Yes, you're right.
Your fix is surely simpler and not concerned by portability issue.

[skvadrik]

Not-so-quick and dirty fix: 7875e6c

[jaydee-io]

Commit 7875e6c fix the problem for me.
Thanks !