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

[Kelly O'Hair]

On 2/22/10 3:54 AM, Andrew John Hughes wrote:
> On 22 February 2010 11:38, Volker Simonis<volker.simonis at gmail.com>  wrote:
>>>>
>>>>> 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'm not on the hotspot team, and I don't follow all the activity
in hotspot land, but I just don't see what the problem is.

I just successfully built the latest OpenJDK6, including the
hotspot provided with it on Fedora 9. No compiler errors,
everything was fine.

So what am I missing here?

-kto


>>>>
>>>> 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.
>>>>
>>>
>>> Right, now that makes more sense.  I have no idea what HSX-16.1 is, so
>>> I'd assumed that it was shorthand for b01 of hs16 rather than some
>>> other repository we can't see.  The only repositories I'm aware of, in
>>> addition to the OpenJDK6 and 7 ones, are the hsx16 base and master
>>> ones.
>>>
>>
>> Hi Andrew,
>>
>> this is the same old story as with HSX 14 (do you remember the mail
>> threads "Switching to HotSpot 14 on OpenJDK6" and "HotSpot shell
>> games"?). The problem is that Sun has its own hg repository for every
>> update release (HSX14 for 6u14, HSX14.1 for 6u15, HSX 14.2 for 6u16)
>> and each of these HSX version has its separate change and build
>> history. What you see in the OpenJDK/HSX repositories is only the
>> first major version of these repositories. Because the HSX
>> repositories with minor versions have a different change history
>> (apart from a common ancestor) it is quite hard to (automatically)
>> merge them into the corresponding OpenJDK HSX repository. And no, you
>> can't see the minor versioned repositories.
>>
>
> Yes, I guessed that after the second mail and my implied point with 'I
> have no idea what HSX16.1 is' was that it shouldn't be discussed on
> public lists if it's not public.  I wouldn't discuss private Red Hat
> repositories on the list -- if we actually had any, which we don't.
>
> Now that the changeset has gone into a *public* repository, things
> should be easier.  I just need this changeset to migrate to master.
>
>> Regards,
>> Volker
>>
>
>
>