[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Busted javahl build on Mac OS X was Re: svn commit: r9415 - in trunk: build/ac-macros subversion/bindings/java

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2004-04-28 04:11:47 CEST

--On Saturday, April 17, 2004 9:45 PM -0500 dlr@tigris.org wrote:

> Author: dlr
> Date: Sat Apr 17 21:44:55 2004
> New Revision: 9415
>
> Modified:
> trunk/build/ac-macros/java.m4
> trunk/subversion/bindings/java/README
> Log:
> Improve location of the jikes Java compiler by allowing for a
> --with-jikes=[PATH|yes|no] argument to configure.

Heh. This borks the 'javahl' build on Mac OS X for me. Here I was
thinking I never finished a corner case, but then I hunted through java.m4
and saw this jikes stuff going, 'Gee, I didn't write this!' - sure enough
adding
'--without-jikes' fixes it for me.

In short, jikes isn't smart enough to find the classes by itself, and the
JAVA_CLASSPATH detection code isn't clever enough on Mac OS X. I don't
know how to programmatically find the classes.jar that jikes need (it's in
'/System/Library/Frameworks/JavaVM.framework/Classes/classes.jar' here on
my box). The default javac doesn't need to be told the classes.jar path,
so that's better, I think.

So, I think we should flip the default to not using jikes - at least on Mac
OS X.

What do you think? -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 28 04:12:40 2004

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.