Dynamically linked libjli for *BSD

Christos Zoulas christos at zoulas.com
Sun May 17 15:30:26 UTC 2015

On May 16,  3:06pm, kurt at intricatesoftware.com (Kurt Miller) wrote:
-- Subject: Dynamically linked libjli for *BSD

| Hi Greg, Christos,
| Currently building the jdk with debug symbols fails on OpenBSD and
| I suspect at least FreeBSD (since it is disabled in the ports tree
| java/openjdk8/Makefile too). This was determined to be caused by
| libjli being statically linked on *BSD. [1]
| Statically linking libjli was a work-around introduced in 1.5 or 1.6
| most likely due to the lack of rpath $ORIGIN support in our runtime
| linkers. All of the BSD's have rpath $ORIGIN support for several
| years now. I propose that we eliminate linking libjli statically and
| remove another difference we have in the build when compared to
| Linux and Solaris. Dynamically linking libjli fixes the build with
| debug symbols.
| Please review/test this diff on FreeBSD and NetBSD and let me know if
| you are okay with the change.

Works on NetBSD. Just a note, $ORIGIN support is not fully implemented
on NetBSD, there is a #ifdef notyet in kern_exec.c... But running java
with a full path in $0 works. I'd say apply it if it works for others.


More information about the bsd-port-dev mailing list