Build error on jdk8/tl project - Thread.o:(.data.rel+0xbc): undefined reference to JVM_SetNativeThreadName
jonathan.gibbons at oracle.com
Mon Mar 26 03:42:11 PDT 2012
Really? I'm not sure I agree. If you have a complete and successful
build of JDK 8, then you should pretty much always be able to use that
as a bootstrap JDK.
That being said, I do not disagree with the general advice to use 7u4 as
the bootstrap JDK.
On 03/26/2012 03:37 AM, Alan Bateman wrote:
> On 26/03/2012 02:25, Weijun Wang wrote:
>> There is completely no harm in setting JDK 8 as BOOTDIR of JDK 8, but
>> I would suggest you using 7u4. If there is anything wrong, you can
>> send us a bug report.
> I don't think we can guarantee that jdk8 will always be buildable
> using another jdk8 build as the bootstrap JDK. There will be times
> were there are API changes in-flight that might mean that langtools
> couldn't build (there were many cases in jdk7 where this was the
> case). So for jdk8 then I think the best (and only sane) advice is to
> use jdk7 as the bootstrap JDK.
> Clearly of course a JDK build needs to be able to build itself and a
> boot cycle build is great test but that may be more than Martijn wants
More information about the build-dev