The VS compiler supports building 64-bit targets on 32-bit Windows/cl.exe but at some point along the jdk build process the newly built bin\java.exe is being used and that should fail on your 32-bit OS.
0.02, Ivan On Aug 26, 2013, at 12:24 PM, Erik Joelsson <erik.joels...@oracle.com> wrote: > > > On 2013-08-26 03:51, David Holmes wrote: >> On 24/08/2013 11:26 AM, Tim Bell wrote: >>> On 08/23/13 02:15 PM, Salter, Thomas A wrote: >>>> Is there any hope of compiling a 64-bit Windows JVM on a 32-bit O/S? >>> >>> We are headed in the other direction with OpenJDK 8 on Windows - >>> compiling both 32 and 64-bit using Windows 2008R2 64-bit as the O/S and >>> Visual Studio 2010 SP1 as the compiler. We have very few 32-bit Windows >>> systems left, and those we have are dedicated to building earlier JDK >>> releases. >> >> That aside though, if the windows 32-bit dev tools support building 64-bit >> binaries (I have no idea if they do) then it should be as simple as >> configuring with --with-target-bits=64. But so far all our cross-compiling >> of this form has been on linux and only tested for building 32-bit on a >> 64-bit host. >> > There is partial support in there, but some details missing. I believe it can > be made to work with some tweaks though. The parameter David suggests is the > correct starting point. > > /Erik > >> David >> >>> Tim >>> >>>> I tried a few options and other tweaks and got as far as configure >>>> compiling a 64-bit fixpath.exe and then discovering that it won't run >>>> on a 32-bit system. >>>> >>>> I don't mind changing the make files but I'm not up for learning how >>>> to generate the configure script. >>>> >>>> Tom Salter | Software Engineer | Java & Middleware Development >>>> Unisys | 2476 Swedesford Road | Malvern, PA 19355 | >>>> 610-648-2568 | N385-2568 >>>> >>>> >>>
