Building 32-bit binaries on Solaris

Alan Bateman Alan.Bateman at oracle.com
Mon Nov 26 01:42:04 PST 2012


On 26/11/2012 08:32, Erik Joelsson wrote:
>
> The documentation surely needs to be updated. I will try to get the 
> biggest out of date info corrected today at least.
>
> The default was changed to be consistent on all platforms. I think 
> that's a good idea, but I wouldn't fight for it if 32bit would still 
> be preferred as default.
>
> Also note that by default, only server version of hotspot is built, so 
> if you want what was default before, you will also need 
> --with-jvm-variants=client,server, which doubles the compile time for 
> hotspot.
I think it's reasonable to default to 64-bit, just awkward on Solaris 
because the 64-bit build overlays over the 32-bit build. I've often 
thought we should move away from this anyway and just have separate 
images like we do on Linux and Windows. I realize there is a 
counter-argument to have both 32-bit and 64-bit in the same image on 
Linux and Windows too, but that is going to be highly problematic when 
we move to modules. As it stands then it looks to me that the new build 
will create a Solaris 64-bit image that is usable, although I see this 
confuses a lot of tests. FYI, in jigsaw/jigsaw then the Solaris 64-bit 
build is a also complete image, no support for overlaying.

-Alan.




More information about the build-infra-dev mailing list