existing the Solaris base, and similarly to what happened with NSPR, made
a bad assumption on undefined behavior. This broke locking in various
places in Java, for example, causing the the debugging support to be
totally broken. It is worth someone who knows the Java codebase taking
a look to see what other things could have been broken by this on
FreeBSD 5.x+.
The assumption is that pthread_mutex_trylock(3) on a default-type
mutex will fail with EBUSY. This assumption is wrong for our
libpthread, which returns EDEADLK if the owner thread is trying to
acquire the mutex again with trylock. The behavior of performing a
locking operation on a self-locked default-type mutex is explicitly
undefined for pthread_mutex_lock(3).
The POSIX specification is still not very clear. It defines
pthread_mutex_trylock(3) in terms of pthread_mutex_lock(3) yet
does not say what the defined behavior should be for a self-locked
pthread_mutex_trylock(3) for any of the various mutex types, so it is
ambiguous whether the result is clearly undefined or clearly to return
EBUSY.
It is a one line change whether or not to make libpthread return
EDEADLK in this case, where it seems that most implementations do not.
Reference: http://www.opengroup.org/onlinepubs/009695399/functions/pthread_mutex_lock.html
The HotSpot code (ab)uses named enums as ints in a number of places.
The problem with this is that according the the C++ spec, the compiler
(essentially) only needs to use an integral type wide enough to hold
the values defined in the enum. Earlier versions of gcc appear to have
just used an int whether they could have got away with a narrower type
or not, hence the code worked as expected. gcc 3.4 now appears to
implement this part of the spec, so using an enum blindly as an int
causes various problems due to overflow.
In this case the enum, Bytecodes::Code, appears to be a genuine enum,
its just assumed to be wide enough to hold an arbitrary int in various
places in the code. The correct fix would be to track down all those
places in the code and fix them. Since there are quite a lot of these
places and 5.3 is close to release for now we just add a value to the
enum set to INT_MAX, forcing the compiler to use at least an int for the
type.
Sleuth work, discussion and code suggestions: peadar
The HotSpot code (ab)uses named enums as ints in a number of places.
The problem with this is that according the the C++ spec, the compiler
(essentially) only needs to use an integral type wide enough to hold
the values defined in the enum. Earlier versions of gcc appear to have
just used an int whether they could have got away with a narrower type
or not, hence the code worked as expected. gcc 3.4 now appears to
implement this part of the spec, so using an enum blindly as an int
causes various problems due to overflow.
This case is particularly bogus since the enums are merely to define
a named integral type within a class (VMReg::Name doesn't even have
any values enumerated in the declaration). So, convert these two
enums to simply be typedef'ed ints.
Sleuth work, discussion and code suggestions: peadar
condition and return NULL". Take account of the NULL in the
appropriate place (which is somewhat worrisome in itself since
ReadChunk() has always had the possibility of returning NULL).
This makes loading a font file a little more resilient to specially
crafted font data which can be used, for example, by an applet to
crash the browser plugin by triggering the assert(). Such an applet
was mentioned on Bugtraq:
http://www.securityfocus.com/archive/1/367331/2004-06-26/2004-07-02/0
and can be found at
http://www.illegalaccess.org/cms/?q=node/view/9
This change stops the browser plugin from crashing.
. Fix some warnings regarding formats in debugging printf's.
(for FreeBSD 4.x neither are defined and for FreeBSD 5.x
O_DSYNC isn't defined). This caused them to be defined to
some bogus values. In particular, O_SYNC would be defined
as 0x800, which is O_EXCL (at least on FreeBSD 4.x). The
result being that the RandomAccessFile class would fail to
open an existing file if you specified "s" as part of the mode.
Fix this by defining O_SYNC and O_DSYNC to O_FSYNC if they
aren't defined.
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
It was last minute change and since this tool (unpack) is not used while
building jdk14 port, I did not paid enough attention to test this change
at -CURRENT system. Sorry.
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).
include/bsd -> include/freebsd in sources, but not reflected
this change in pkg-plist)
Reported by: Holger Kipp <Holger.Kipp@alogis.com>,
Kunihiro Arai <kunihiro-arai@seagreen.ocn.ne.jp>
. Put the MD JNI headers in include/freebsd _not_ include/bsd. This
brings the 1.4 port in line with 1.1, 1.2 and 1.3, and arguably inline
with Solaris and Linux.
Not-objected-to by: phantom
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
