> These are just the build systems used to create the builds. > But yes, as far as I know, I had assumed that there is only a 64bit VM and > only a server VM.
jdk7u-osx is 64 bits alone for now. Just rebuilt it after latest commit to check and even with -d32, JVM still report as 64bits : mbp:~ henri$ java -version openjdk version "1.7.0-u4-b01" OpenJDK Runtime Environment (build 1.7.0-u4-b01-20111206) OpenJDK 64-Bit Server VM (build 23.0-b06, mixed mode) mbp:~ henri$ java -version -d32 openjdk version "1.7.0-u4-b01" OpenJDK Runtime Environment (build 1.7.0-u4-b01-20111206) OpenJDK 64-Bit Server VM (build 23.0-b06, mixed mode) Should it be fixed and restored like it was on macosx-port ? 32bits VM on OSX will be enough for 32 bits kernel system (even if OSX know how to handle 64bits Apps under 32bits Kernel) > Even if we built a 32bit or additional VM, that would happen in the one build > target, and testing > would them have more variations. But I'll avoid that complication until we > reach that bridge. > > -kto > > On Dec 6, 2011, at 7:03 AM, Henri Gomez wrote: > >> macosx_x64_10.7 ? >> >> Does it means there won't be a 32/64 bits JVM ? >> >> >> 2011/12/6 David Holmes <[email protected]>: >>> Hi Kelly, >>> >>> >>> On 6/12/2011 1:19 PM, Kelly O'Hair wrote: >>>> >>>> >>>> For the jdk7u-osx forest (Mac port): >>>> >>>> 7117110: Remove target 1.5 from jaxp and jaxws repo builds for mac >>>> 7118095: Add macosx targets to make/jprt.properties file >>>> http://cr.openjdk.java.net/~ohair/openjdk7/jdk7u-osx-make/webrev/ >>>> >>>> The make/jprt.properties file changes only impact JPRT. >>> >>> >>> Looks okay to me. >>> >>> I really like the new(?) TESTNAME substitution mechanism! >>> >>> I'm wondering though why the full list of build targets had to be set in >>> each of the jprt.properties file? Isn't it sufficient for the JPRT system >>> itself to define the base set of targets? >>> >>> David >>> >>>> -kto >>>> >>> >
