override the MAKEFLAGS ARCH value in the main HotSpot Makefile. Fix
this by passing in a blank MAKEFLAGS up front so there is nothing to
(try to) override.
Submitted by: truckman
Requested by: kris
We switched FreeBSD-5.x port to libkse as default threading library before
releasing of patchset 6, but users who has most of stuff linked against
libc_r and attempted to use jdk linked against libkse got into local hell
of threading libraries mix. So, rollback to libc_r by default and add
PTHREAD_LIBS support for this port.
IMPORTANT: In order to use libkse as threading library for jdk14 you
have to use rtld's libmap feature or recompile your ports stuff (like
mozilla) with libkse.
NOTE: libkse still has issues with java debug support, so if you're going
to use debuging (JVMDI) stuff - leave with libc_r for now.
2. Disable IPv6 support by default. Unfortunatelly due to security reasons
IPv4-to-IPv6 addresses mapping is disabled by default in FreeBSD-5.x, so
those who would like to use Java Networking stuff had to manually
enable it. To make jdk14 port more user-friendly IPv6 is disabled now
on compile time. Those who need this stuff enabled have to use WITH_IPV6
compile time option.
3. Add MINIMAL compile option. If this option is used to build
jdk14 port then plugin, javaws and demos stuff will not be installed
and/or packaged. Also (as noted in [5]) X11 runtime dependancy will
not be registered into built package.
4. Strip runtime depends of jdk14 port. There's no need to require open-motif
to be runtime depends since libXm is staticly linked into libawt.so.
5. Make X11 runtime dependancy conditional (via urwfonts) in !WITHOUT_PLUGIN
case only. This should affect only prebuilt package users: there's no
need to install X11 libraries if you're going to use non-GUI stuff only
(i.e. tomcat or jboss)
6. Add ${LOCALBASE}/lib to the deafult search path for JNI libraries.
7. Bump PORTVERSION
Reported by: many [1]
Submitted by: glewis [6]
Requested by: marcus [6]
configuration file and behave appropriately if its -1. Fixes a SEGV
caused by ignoring the return value and just carrying on.
. Bump PORTREVISION.
PR: 61392
Important changes since last patchset:
. jdk14 port is now JDK 1.4.2 based!
. JavaWS distributing with jdk
. Runway problem fixed (fork() is no more problem for java apps)
. Sound support updated
. IPv6 support overhauled
. Drag'n'Drop support fixed (require open-motif mods)
As for now there's no more outstanding issues with this port!
FreeBSD port is also got a important of changes:
. optimized setup is now default (to get debuging bins/libs use WITH_DEBUG)
. bootstrap jdk autodetection. If WITH_LINUX_BOOTSTRAP is not set, then
it checks all known to work JDKs installed. If nothing found, forces
to install of linux-sun-jdk14
. Because of above change there's no NATIVE_BOOTSTRAP option anymore. If
native jdk14 is installed, it will be used by default.
processes problem for people who use Runtime.getRuntime.exec() method
and related things. Least five people reported that this patch fixed
problem for them.
IMPORTANT: I'd also suggested to all jdk14 users who runs FreeBSD 4.x
and use libc_r at FreeBSD 5.x to upgrade.
. Stop removing "src.zip" from installation bundle. Since -p4 it builds
correctly and there's no reason to forbit people to use it.
. Bump PORTREVISION.
. Add j2se/ext/plugin/build/solaris/GNUmakefile to PTHREAD_FILES. Should
fix plugin compilation on -CURRENT. Mea culpa.
PR: 58269
Submitted by: Scott Dodson <sdodson@sdodson.com>
. Use ${PTHREAD_LIBS} rather than -pthread or -lc_r.
. Install system preferences to avoid annoying and constant error messages.
Approved by: phantom (the update, anyway)
start native JDK port build. linprocfs mounted become pre-requisite of
build after Linux SUN JDK port was updated to 1.4.2.
Add run-time (pre-build) check for linprocfs mounted as well.
Bump space requirements note about disk space required for build of
whole JDK 1.4.1 port and package to more appropriate value (as reported
by many people).
for JDK 1.4.1. This is complete and close to production quality
native JDK with both working client and server native JVMs. Local micro
benchmarks shown very little difference between Linux and FreeBSD JVMs in
speed.
One of important points of this patchset that it marks point when we are
very close to passing of Sun TCK tests. Currently about 20 of >27000 tests
are known to be broken (tests were run at -STABLE). If testing of this
patchset will be smooth and founding of this work will be continued we
may expect to have binary distribution of JDK 1.4.1 in April or begining
of May.
BUT, don't forget that even TCK tests can't cover all possible problems
and this is -beta patchset. Keep your eyes open and report your problems
to freebsd-java mailing list or to me directly!
* About supported FreeBSD releases:
Altough 4.8-RELEASE will be first officially supported FreeBSD release,
you may use JDK 1.4.1-p3 at stock post-02-Feb-2003 -STABLE or -CURRENT.
You also may use it at post-07-Jan-2003 -STABLE and -CURRENT (including
5.0-RELEASE), but it's required to apply libc_r patch, distributed with
patchset3 archive, and rebuild libc_r first.
* About compiler:
This port is supposed to be built with stock FreeBSD compiler (3.2.[12]
for -CURRENT and 2.95.4 for -STABLE)!
* Following issues are known, but not yet addressed:
. IPv6 networking. IPv6 support is disabled in this patchset.
. Asian languages support. Patches are welcome!
. K6 (586-class) processors support. There're issues with building on
old K6 processors. If you've problems with 586-class machines other than
K6 - please let me know.
. Mozilla plugin is not yet ported.
* Following areas should be used with increased attention:
. Java Virtual Machine Profiling Interface (JVMPI)
. Java Virtual Machine Debugging Interface (JVMDI)
. Host Porting Interface (HPI)
If you have problems with these interfaces please let me know.
* THANKS!
I would thank very much to FreeBSD Foundation, without which support
and sponsorship JDK 1.4.1 port would not happen in such timeframes (less
than 2 months).
Sponsored by: FreeBSD Foundation
Approved by: portmgr
2. Enable compiling the HotSpot JVM. This is experimental and there are a
number of caveats with its use that are reported by the port. The flag
to enable this is WITH_HOTSPOT.
3. Try to pick some OSVERSION settings appropriate for the current native
threads implementation.
PR: 47397 (2)
Submitted by: Munehiro Matsuda <haro@h4.dion.ne.jp> (2)
.if defined(BATCH) || defined(PACKAGE_BUILDING)
IGNORE= "You can not legally distribute binaries"
.endif
This was superfluous and inhibiting package builds of things that
depend on the port. Having RESTRICTED and NO_CDROM is enough to
ensure that a package will not appear on the FTP site or a CDROM
(it will be built and used as a basis for other packages to build
with, but will be deleted at the end of the build run).
Requested by: kris
Reviewed by: portmgr (silence)
PR: 42758
TAR and add gtar to BUILD_DEPENDS unless the OSVERSION is old enough.
Small tweak by me to note that sobomax has MFC'ed the tar update.
Submitted by: Mikhail Teterin <mi@aldan.algebra.com>
