It's making unwarranted assumptions about my Java setup:
#!/bin/sh -ev
mkdir build
cd build
# old-location
# JAVA_HOME=`/usr/libexec/java_home`
JAVA_FW=/System/Library/Frameworks/JavaVM.framework
JAVA_HOME=$JAVA_FW/Home
test -d $JAVA_HOME && test -x $JAVA_HOME || \
{ echo "$JAVA_HOME not found." ; exit 1 ;}
/System/Library/Frameworks/JavaVM.framework/Home not found.
$ /usr/libexec/java_home
/Library/Java/JavaVirtualMachines/jdk1.7.0_45.jdk/Contents/Home
I'm guessing that parsing `/usr/libexec/java_home` is a better way to go
here for portability and to deal with the wacked out Java in OS X.
--
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/
------------------------------------------------------------------------------
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users
