RFR: Solaris 64-bit images

[Kelly O'Hair]

On May 21, 2012, at 7:40 AM, Alan Bateman wrote:

> On 21/05/2012 14:28, Chris Hegarty wrote:
>> There is currently an issue with the Solaris 64-bit image. To date Solaris 64-bit bundles need to overlay the 32 bit bundle. This doesn't currently make sense in the modular world and more thought needs to go into how we want to handle this long term.
>> 
>> What I have done in the webrev is to temporarily disable the creation of the Solaris 64-bit commands in the amd64/sparcv9 directories, and fixup paths to find the appropriate native libraries. This will build a 64-bit only bundle and jmod files, similar to what we have on other platforms.
>> 
>> For now, I think this is a reasonable solution until we can address issues around how to want to handle this long term.
>> 
>> http://cr.openjdk.java.net/~chegar/jigsaw/solaris64_webrev.00/webrev/
>> 
>> -Chris.
> Just to add to Chris's comments, these changes gives us a solaris-x64 modules build that has the same layout as what we have for linux-x64, windows-x64, and macosx-x64. There has been suggestions that we should have one image that supports both 32-bit and 64-bit but that raises questions as to whether it has one or two system module libraries. For now having a separate 64-bit image makes the most sense.
> 

If the solaris 64bit builds will be full jdk builds, that means that those builds will take considerably longer (all the duplicate javac compiles)
and the resulting 64bit bundles will be larger. Solaris SPARC is already a long pole on building, this could make it worse.

If for the sake of simplicity, if we want to go down this 'full jdk for all' strategy, as a more permanent thing,
I'm ok with that.  But is that what you are saying?  If so, we may need to adjust our SPARC orders and pray that
we actually get what we order some day. :^(

-kto

> Chris - I looked at the changes and they look okay to me. I also grabbed the patch and it built a solaris-x64 image as I expected. I'm happy to push the changes for you. One small thing is that we have a couple of tests (launcher and JDI tests come to mind) that launch via amd64/bin or sparcv9/bin. We might need to add them to the ModulesProblemList.txt.
> 
> -Alan.