Build attempts to install /usr/local/jvm/ binary in an invalid location on Mac OS X

Magnus Ihse Bursie magnus.ihse.bursie at
Tue Apr 14 09:46:39 UTC 2015

Hi Martijn,

On 2015-04-14 10:05, Martijn Verburg wrote:
> Hi all,
> Using Configuration:
> using configure arguments '--with-boot-jdk=/Library/Java/JavaVirtualMachines
> /jdk1.8.0_40.jdk/Contents/Home/ --with-tools-dir=/opt/local/bin/ --with-
> toolchain-type=gcc --with-freetype-lib=/usr/X11/lib/ --with-freetype
> -include=/usr/X11/include/freetype2/'.
> -----
> It attempts to install a binary at /usr/local/jvm/openjdk-1.9.0-internal.  /
> usr/local/jvm doesn't exist on Mac OS X and can't be created (need sudo)

The "install" target is probably in need of a lot of TLC. I wouldn't be 
surprised if it has bit-rotted. However, in all normal circumstances, 
running it *will* require root/sudo credentials -- the whole point is to 
install the newly built JDK into a system-wide location.
The suggested commands for doing this is:
 > bash configure --prefix=...
 > make all
 > sudo make install

so that you don't run more of the build than necessary as root. Also 
note that, in theory, you should be able to select another location 
using the build-in autoconf --prefix option. If you select a path 
writable by your user, you will not require the sudo part. I'm not sure 
how well tested that is, though.


More information about the build-dev mailing list