This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Making the testsuite work for Mauve without installing


>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:

Mark> I don't mind really learning DejaGNU, Tcl and spec files to come
Mark> up with a better test framework. But then I need some examples
Mark> of setups that people actually use since I don't have a clear
Mark> picture of how/why to test an installed toolchain inside the
Mark> build dir.

My understanding is that when we do this internally, we always run
dejagnu in a fresh directory away from both the build and install
trees.  So if your change is robust in the face of that, then I think
it will be ok.  Maybe you could just change your patch to test for the
existence of $objdir/../libgcj-3.1.jar before adding a -I for it?
What do you think of that?

Also, we haven't done this kind of testing recently (this year at
least).  I assume that I'll end up fixing bugs in it if we need it to
work again.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]