64 Bit SBCL under Windows

[candera]

I recently moved to a (smokin' fast) new machine, but I'm running 64-bit Windows, so SBCL no longer works for me. I've been able to find out that "a port is in progress", but no more information than that. Anyone know where this effort is at?

[findinglisp]

I though 64-bit Windows could also run 32-bit programs? Can't you continue running the old version until a full 64-bit Windows port is available?

[candera]

I wish. Doesn't work. I get this error:

VirtualAlloc: 0x57.
fatal error encountered in SBCL pid 4304:
os_map: VirtualAlloc failure

Some of the APIs are definitely different under x64 - I've had to recompile a few of my C++ programs, and even one of my .NET ones that did interop. Given the switch to 64-bit, it's hardly surprising that VirtualAlloc is one of the ones that have changed.

But it's entirely possible that there's a way to make a x86 image run under x64. If so, I don't know what it is. I was hoping someone who does might have tossed together a moderately recent build of SBCL that I could use.

[findinglisp]

Hmmm... interesting. I know that SBCL does a bunch of strange stuff at startup to load the core file. I don't know the details, but it sounds like some of that isn't compatible with 64-bit.

[malkia]

I recently moved to a (smokin' fast) new machine, but I'm running 64-bit Windows, so SBCL no longer works for me. I've been able to find out that "a port is in progress", but no more information than that. Anyone know where this effort is at?

Don't have a 64-bit Windows in front of me, but have you tried doing tweaking the Compatibility Settings (and now I'm in front of my Mac, so I can't tell you how to get to them (Properties?))

That google search might help

http://www.google.com/search?client=saf ... 8&oe=UTF-8

[candera]

I recently moved to a (smokin' fast) new machine, but I'm running 64-bit Windows, so SBCL no longer works for me. I've been able to find out that "a port is in progress", but no more information than that. Anyone know where this effort is at?

Don't have a 64-bit Windows in front of me, but have you tried doing tweaking the Compatibility Settings (and now I'm in front of my Mac, so I can't tell you how to get to them (Properties?))

That google search might help

http://www.google.com/search?client=saf ... 8&oe=UTF-8

Not a bad idea, but unfortunately it doesn't work.

I think the thing I'm up against here is that at the API level, it's a different operating system, and one that is currently unsupported. Someone will probably get around to hacking together a build in a few months. Maybe I'll try my hand at it - it would certainly be highly educational.

[malkia]

Thanks, Candera!

That's good to know - in the company I work we have only one tool that uses 64-bit machine, simply because we are running out of 2GB on it (it's for doing global illumination and lots of memory is spent there), but this is as far as my 64-bit Windows knowledge goes. I would've expected from Microsoft more transparency......

[amos]

It may be using a sledgehammer to crack a nut, but you could run Virtual copy of Linux in something like Virtual Box, and run a 64 bit copy of SBCL in there.

Cheers
Amos

[candera]

It may be using a sledgehammer to crack a nut, but you could run Virtual copy of Linux in something like Virtual Box, and run a 64 bit copy of SBCL in there.

Cheers
Amos

Oh, I'm doing something like that now (remote X session to a Linux box via XMing, which rocks). I just want to avoid it if I can.

It's really a shame that Windows is such a ghetto for most Lisp implementations.

[nikodemus]

This

http://article.gmane.org/gmane.lisp.ste ... evel/10686

patch may be of use to you. (It's likely to be merged to CVS soonish.)

Cheers,

-- Nikodemus Siivola

PS. I don't regularly read these forums, so I am unlikely to see any responses on this thread.