FreshPorts -- java/sablevm

SableVM implements the Java virtual machine specification, second edition. SableVM is a bytecode interpreter. It's goals are to be reasonably small, efficient, and fast, as well as providing a well-designed platform for doing research into different algorithms for bytecode interpretation, garbage collection, memory management, etc. WWW: http://www.sablevm.org/

pkg-plist

make generate-plist

Expand this list (25 items)

/usr/local/share/licenses/sablevm-1.13_12/catalog.mk

/usr/local/share/licenses/sablevm-1.13_12/LICENSE

/usr/local/share/licenses/sablevm-1.13_12/LGPL21

bin/jar-sablevm

bin/java-sablevm

bin/javac-sablevm

bin/sablevm

include/sablevm/jni.h

include/sablevm/jni_system_specific.h

lib/libsablevm-1.13.so

lib/libsablevm.so

lib/sablevm/bin/jar

lib/sablevm/bin/java

lib/sablevm/bin/javac

lib/sablevm/bin/jdb

lib/sablevm/include/jni.h

lib/sablevm/include/jni_system_specific.h

lib/sablevm/jre/bin

man/man1/java-sablevm.1.gz

man/man1/sablevm.1.gz

share/sablevm/AUTHORS

share/sablevm/LGPL-2.1

share/sablevm/LICENSE

@postexec /sbin/ldconfig -m /usr/local/lib

@postunexec /sbin/ldconfig -R

Collapse this list.

To install the port: cd /usr/ports/java/sablevm/ && make install clean
To add the package: pkg install sablevm

NOTE: FreshPorts displays only information on required and default dependencies. Optional dependencies are not covered.

- Reset maintainership. See ports/164941. - Fix conflicts with java/classpath. Note security provider configuration is moved to ${PREFIX}/lib/security/SableVM.security. This file is always loaded first because the short vendor name is SableVM. If it does not exist, then classpath.security is loaded (java/security/Security.java). - Reduce Makefile headers, add licenses, and convert to optionsNG.

- Add LDFLAGS to CONFIGURE_ENV and MAKE_ENV (as it was done with LDFLAGS) - Fix all ports that add {CPP,LD}FLAGS to *_ENV to modify flags instead PR: 157936 Submitted by: myself Exp-runs by: pav Approved by: pav

-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22. -Update libtool and libltdl to 2.2.6a. -Remove devel/libtool15 and devel/libltdl15. -Fix ports build with libtool22/libltdl22. -Bump ports that depend on libltdl22 due to shared library version change. -Explain what to do update in the UPDATING. It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop and applications in the runtime. With help: marcus and kwm Pointyhat-exp: a few times by pav Tested by: pgollucci, "Romain TartiÃ¨re" <romain@blogreen.org>, and a few MarcusCom CVS users. Also, I might have missed a few. Repocopy by: marcus Approved by: portmgr

Bump portrevision due to upgrade of devel/gettext. The affected ports are the ones with gettext as a run-dependency according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT in Makefile (29 of them). PR: ports/124340 Submitted by: edwin@ Approved by: portmgr (pav)

- Update to 1.13 - Take maintainership - Split classpath into separate port - Switch to libffi-devel to allow build on !386 PR: ports/118288, ports/118312 Submitted by: Bjoern Koenig <bkoenig@alpha-tierchen.de>

Mass-conversion to the USE_AUTOTOOLS New World Order. The code present in bsd.autotools.mk essentially makes this a no-op given that all the old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in exactly the same way as USE_AUTOTOOLS itself. Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME team -- all GNOME 2.12.x ports use it. Preliminary documentation can be found at: http://people.FreeBSD.org/~ade/autotools.txt which is in the process of being SGMLized before introduction into the Porters Handbook. Light blue touch-paper. Run.

Whoa there, boy, that's a mighty big commit y'all have there... Begin autotools sanitization sequence by requiring ports to explicitly specify which version of {libtool,autoconf,automake} they need, erasing the concept of a "system default". For ports-in-waiting: USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13 USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213 USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14 Ports attempting to use the old style system after June 1st 2004 will be sorely disappointed.

libtool uber-patch * kill devel/libtool and move to devel/libtool13, upgrading to 1.3.5 * upgrade repo-copied devel/libtool14 to 1.4.3 * break out libltdl into its own separate port * move to version-numbered binaries/scripts (ie: there is *no* 'libtool' any more -- USE_LIBTOOL and USE_LIBTOOL_VER are your friends) Approved by: portmgr (kris) - for the bsd.port.mk hooks Tested by: bento 4-exp builds (repeatedly)