Am Montag, 29. M�rz 2004 14:44 schrieb C. Brian Jones:
On Mon, 2004-03-29 at 01:35, Michael Koch wrote:
Am Sonntag, 28. M�rz 2004 21:29 schrieb Etienne Gagnon:
Mark Wielaard wrote:
Unless running with --force the auto* tools shouldn't override these files so normally you won't see any diffs when following the HACKING instructions. But there is no particular reason. So please remove them. Make sure to update the HACKING file and send a message to the list how to regenerate these when you do.
I have added a ./autogen.sh script that calls the auto* tools with the appropriate arguments, and updated the HACKING files accordingly.
So, those of you that "cvs up", simply type: ./autogen.sh after updating.
I really wonder if this primitive script really works on some non-linux platforms. I will commit an improved version later.
Why not just use autoreconf which is usually installed with the autotools.
Yeah, I totally forgot about this. In the HACKING file I read this:
The autoreconf script does not always run these as might be expected.
Does this still apply ? I think it would be best to just use "autoreconf" and give good instructions for uncommon cases in HACKING.
It works well enough with up-to-date versions of autotools. The only problem is to teach autoreconf about needing to patch libltdl, and such things, which is why we have an autogen.sh script in kaffe.
cheers, dalibor topic
_______________________________________________ Classpath mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/classpath
