From: Anton K. <an...@sw...> - 2011-08-18 11:27:39
|
David Lichteblau <da...@li...> writes: > Not certain whether it answers your question, but: > > SBCL from git has just sufficiently many of your fixes so that it can be > built using Wine, with MSYS/MinGW installed into Wine as usual. Well, actually, you could have been certain that I know it -- for a whole lot of reasons. I'm watching SBCL's upstream `trunk' closely and merge frequently; I pay special attention to what you're doing or planning w.r.t SBCL on Windows; I look closely into upstream commits that affect the code that I've touched a lot, and my own fixes coming back are frequently of this kind; I /have/ to resolve conflicts when my earlier code collides with my later code; etc., etc.. > If you meant actual use of gcc as a linux->windows cross-compiler -- > it's certainly possible, but I've stopped doing it, since "wine sh > make.sh" works just as well and doesn't require changes to the > scripts. That's really good news! I had no problem with native Mingw/GCC by itself, but the /userland/ from MSYS failed so consistently over years that I've given up even /trying/ to run it with Wine some years ago. (BTW, for some major aesthetical and minor technical reasons, I would still prefer to have a build process that avoids `sh' and makefiles entirely, with the host CL implementation 'scripted' in Common Lisp -- something like the way ClozureCL is built). -- Regards, Anton Kovalenko +7(916)345-34-02 | Elektrostal' MO, Russia |