libera/#sbcl - IRC Chatlog
Search
6:26:02
andrew77
I'm trying to compile SBCL using MinGW under Wine - I know it is pretty weird setup, but I even got it working at some point last year. Now, with current git master, I'm getting weird errors when building contribs, namely SB-FASL::INVALID-FASL-VERSION which suggest that target SBCL tries to load UIOP fasl from host SBCL (I'm using 1.4.14 windows
6:26:02
andrew77
build to bootstrap) instead of using bundled UIOP source. Here's the full build log: https://pastebin.com/C9585Y5c . Any advice?
9:00:46
Krystof
do you have SBCL_HOME set in the environment? That affects where (require ...) looks for contribs
9:15:37
Krystof
it wouldn't surprise me to find that the installer for sbcl 1.4.14 set SBCL_HOME in the environment in an unexpected way
9:25:00
andrew77
Huh, weird: the built sbcl fails with unhandled exception, "Unhandled page fault on write access to 0000000000008060 at address 000000014001EE82 (thread 0009)"
9:25:01
andrew77
And yes, as a matter of fact wine has SBCL_HOME env var set to "Program Files" dir. I'll try to unset it and see if that works
12:45:36
stassats
i guess i need to materialize my idea of not only looking everywhere for SBCL_HOME, but also checking if the stuff there is compatible
13:31:17
Krystof
maybe win32 programs' environments have the win32 environment override the mingw environment?
13:33:20
Krystof
I wouldn't be surprised at all to find that wine overrides the environment for its children
13:33:47
Krystof
this is an sbcl running on unix (I think) with wine configured to automatically interpret windows binaries?
13:34:35
Krystof
so ../../src/runtime/sbcl --core ../../output/sbcl.core really means 'wine ../../src/runtime/sbcl --core ../../output/sbcl.core', so it makes sense that wine would set up the environment for its children
13:48:46
stassats
i hope "Unhandled page fault on write access to 0000000000008060 at address 000000014001EE82 (thread 0009)" can be blamed on wine too
15:01:45
andrew77
@stassats yes, the unhandled page fault was due to freshly build sbcl not being able to locate, erm, its runtime (core and everything); run-sbcl.sh works just fine
15:31:23
andrew77
I've already worked the problem at hand around by unsetting SBCL_HOME, but thanks :)
15:32:39
andrew77
I'm currently dealing with the make-windows-installer script, and, oh my god, why on earth Wix?.. I mean, NSIS was always choice number 1 regarding building windows installers
15:33:18
andrew77
I mean, the damn thing needs .NET, which is entirely different level of PITA for wine
15:35:07
stassats
but what if, gasp, somebody is not using javascript? make it lead to a page with two links?
15:36:43
andrew77
Got it. Then installer it is:) I mean, it is fine for end user, it is just building of that which is troublesome