HotSpot 16 on OpenJDK6 build failure (was hg: jdk6/jdk6/hotspot: 3 new changesets)

[Daniel D. Daugherty]

Andrew John Hughes wrote:
> 2010/2/17 Andrew John Hughes <gnu_andrew at member.fsf.org>:
>   
>
> Can we please have a solution for this?
Actually, I've been working on getting this fix into HSX-16
even though I'm on a road trip (and on vacation).


> This changeset is NOT in the
> hs16 master and is causing the OpenJDK6 build to fail once the hs16
> master is imported, thus blocking our progress on preparing b19.
>   

I previously said that I pushed this fix to HSX-16.1 which is not
the same as HSX-16. I never said that this fix is in the HSX-16
master.


> Using hs16 directly with OpenJDK6 works -- we have been doing this for
> sometime.  As shown by the diff I posted, this conflicting changeset
> is local to OpenJDK6.
>   

Yup. I thought I was doing the "right thing" by fixing this bug
in OpenJDK6 also in addition to HSX-16.1 and HSX-17. Now I'm
starting to wonder why I bother doing things for OpenJDK6 at all.


> Is there a suitable default value for version so that we can
> reintroduce the JvmtiEnv() constructor that was removed by your
> changeset?
>   

When I ported the changeset to HSX-16, there was no need for a
no-args constructor. I previously asked why you needed one and
I don't see that answer in this e-mail thread. Perhaps I missed
your reasons.

I'll be pushing the ported changeset to HSX-16 baseline once I
get back to Colorado. Right now I'm in New Mexico and expect to
get home in 9-10 hours depending on the snow...

Dan