pre-inst-guile-env added along with test-suite/standalone

[Rob Browning]

For a while I had been debating how to handle standalone tests given
our current testing framework which only accommodates scheme code tests
and runs them all in one guile process.

For now I've decided to punt on the issue, and I've created
test-suite/standalone which runs tests at "make check" time in the
traditional "automake" fashion, completely independently of guile-test
and check-guile.  In this approach, each test is standalone, binaries
or scripts may be used (and just need to be added to Makefile.am's
TESTS variable), and the exit code from the executable indicates the
result.  Note that these tests will only be run via "make check".
since check-guile doesn't know about them.

To accommodate the standalone tests, in particular to accommodate
standalone binary tests, I've also added pre-inst-guile-env which acts
like the traditional "env", but sets up the environment (PATH,
GUILE_LOAD_PATH, LD_LIBRARY_PATH, etc.) for the pre-installed Guile.
Note that at the moment, pre-inst-guile-env.in is nearly identical to
pre-inst-guile.in.  I suspect that we might want to change
pre-inst-guile.in to just contain a trivial invocation of guile via
pre-inst-guile-env eventually.

With respect to new tests in standalone, in addition to adding a
regression test for a recent bug, I've migrated and updated the c-api
and asmobs tests that used to be in test-suite/tests, but weren't ever
being run.

I'm not sure what we'll want to do about our testing longer-term, but
this makes it easy to add new tests, and I felt like that was
important *now*.  See test-suite/standalone/README and the
standalone/Makefile.am for more information.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592  F9A0 25C8 D377 8C7E 73A4