From: Godmar Back (gback@cs.utah.edu)
Date: Thu Sep 10 1998 - 13:43:20 EDT
> > For instance, I checked out japhar. They don't even have a configure
> > file in their CVS. The result: it doesn't work (aclocal fails), despite
> > the fact that I have the required versions of automake and autoconf
> > installed. So much for that piece of GNU wonderware. I sent them
> > mail asking about it.
>
> Yeah, that sounds like a lousy experience, but to me it means
> "there's a bug" more than "the model is broken".
>
Well, it turns out you needed to have your aclocal/automake
use perl version 5, as opposed to version 4. The script asks for
#!/usr/bin/perl, which happens to be perl 4 on our installation
(as opposed to /usr/local/bin/perl, which is perl 5...)
Of course, automake doesn't fail if it doesn't have perl 5,
and maybe it even works in most cases, except for how they use it
it japhar. Whose fault is it?
About the philosophical point: It's like airplane design: you should
built in redundancies wherever it's cheap and makes sense.
So, I checked in the new external_wrappers.h handling. Hopefully,
this didn't break things.
BTW, we licensed javaspec here. I have the CD and hope to be able
to run some benchmarks shortly.
- Godmar
This archive was generated by hypermail 2b29 : Sat Sep 23 2000 - 19:56:56 EDT