On 10/10/13 13:50, Eric Bavier wrote:
> I was working on packaging AutoGen for Guix (www.gnu.org/software/guix)
> and came across a number of failing tests with `make check` (19 of 24 in
> autoopts failed).
I am now wondering how that might have happened.
The "init_tests" function should not be run with "set -e" active.
Failing to test the results:
> f=`\cd ${LIBGUILE_PATH}/../bin && pwd`
> PATH=${f}:${PATH}
should just lead to a spurious ":" appended to the start of $PATH.
The following should be a little bit more rigorous:
> f=`\cd ${LIBGUILE_PATH}/../bin 1>/dev/null && pwd` || {
> f=`command -v guile | sed 's@/[^/]*$@@'`
> test -d "$f" || die "cannot find guile exe"
> }
> case ":${PATH}:" in
> *":${f}:"* ) : ;;
> * ) PATH=${f}:${PATH} ;;
> esac
But "errexit" should still not be set.
For now, I've not included --with-libguile-path just because of time.
Please try the new pre-release and if you have troubles, I'll try
to get to the "with" thing.
Thanks - Bruce
http://autogen.sourceforge.net/data/autogen-5.18.2pre7.tar.xz
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Autogen-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/autogen-users
