Hi Magnus, Thanks for the detailed explanation, appreciated as always! I'll just execute make clean images for now and reference the binary via its absolute path as required.
Of course I'm now onto the next build error ;-). But I'll open a separate thread for that tomorrow. Cheers, Martijn On 14 April 2015 at 11:46, Magnus Ihse Bursie <magnus.ihse.bur...@oracle.com > wrote: > 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. > > /Magnus > >
