Hi Nicolas,> Yes, there has been an incompatibility change recently between LLVM and VMKit. Please use revision 100087 of LLVM until I find a workaround.OK, done.> Also, running on Snow Leopard is untested (VMKit does not have support for GC on 64bits), but should work without a GC. You can also try to compile on 32bits.How would I run VMKit without GC? Compiling for 32 bits is not an attractive option. The problem is the GNU classpath library, which has some unpleasant dependencies, in particular GTK+. I get them through MacPorts, which compiles 64-bit only on Snow Leopard. I'd have to install all that by hand to get 32-bit versions. I guess I'd rather work with a 32-bit Linux running under VirtualBox. Long live virtualization! ;-) Konrad.
Hi Konrad, On Fri, Apr 2, 2010 at 6:38 PM, Konrad Hinsen <konrad.hinsen at fastmail.net>wrote:> > > How would I run VMKit without GC? >VMKit just falls back to malloc when it detects that the machine is 64bits.> > Compiling for 32 bits is not an attractive option. The problem is the GNU > classpath library, which has some unpleasant dependencies, in particular > GTK+. I get them through MacPorts, which compiles 64-bit only on Snow > Leopard. I'd have to install all that by hand to get 32-bit versions. I > guess I'd rather work with a 32-bit Linux running under VirtualBox. Long > live virtualization! ;-) > >Yes, running a 32bits virtualized system should work just fine. Nicolas> Konrad. > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100402/f51ec39c/attachment.html>
Hi Nicolas,>> How would I run VMKit without GC? > > VMKit just falls back to malloc when it detects that the machine is > 64bits.OK, I think I can handle that ;-)> Yes, running a 32bits virtualized system should work just fine.I first tried something else: compiling on an older Mac (10.5, 32 bit compilers) and copy the binary over to the 64-bit Mac. Of course I ran a quick test on the 10.5 machine to make sure that it works - but it doesn't: ~/Temp> javac hello.java ~/Temp> java -cp . HelloWorld Hello World! ~/Temp> j3 -cp . HelloWorld terminate called without an active exception Abort trap Here's hello.java: class HelloWorld { public static void main(String args[]) { System.out.println("Hello World!"); } } Any ideas? Konrad.