This is the mail archive of the
java-patches@gcc.gnu.org
mailing list for the Java project.
Re: [testsuite, build] Convert boehm-gc testsuite to DejaGnu (PR boehm-gc/11412)
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: gcc-patches at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, Hans Boehm <hans_boehm at hp dot com>, Paolo Bonzini <bonzini at gnu dot org>, Janis Johnson <janis dot marie dot johnson at gmail dot com>, Ben Elliston <bje at gnu dot org>, Ralf Wildenhues <Ralf dot Wildenhues at gmx dot de>
- Date: Wed, 05 Jan 2011 20:44:13 +0000
- Subject: Re: [testsuite, build] Convert boehm-gc testsuite to DejaGnu (PR boehm-gc/11412)
- References: <ydd62u3p6m7.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 05/01/2011 18:06, Rainer Orth wrote:
Hi Rainer,
> * The primary complication of the boehm-gc testsuite is the
> staticroottest testcase, which depends on a shared library.
> Currently, libtool is used to build that and I think that's the right
> decision rather than duplicating all of libtool's knowledge in
> DejaGnu.
>
> Unfortunately, DejaGnu knows nothing about libtool yet, and I'm still
> struggling with the right way to integrate it. For the moment (though
> I fear that wrong, over-complicated) I've chosen to add two additional
> keywords (ltassemble and ltlink) to match assemble and link, but for
> .la, .lo files instead. I'm open for suggestions for better ways to
> handle this, though.
Perhaps just build it in the makefile, as at present, and make the .la file
a dependency of the check target, so that it gets built before starting the
testrun? (Or conceivably if worried about it failing to build on some target
and that stopping the tests from running, build it using a recursive $(MAKE)
invocation, using the "-" prefix to ignore errors?)
cheers,
DaveK