libera/#sbcl - IRC Chatlog
Search
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
19:47:32
waleee
Is a large number of "Found string NIL" lines followed by "Found string "Can't displace an array of type ~/sb-impl:print-type-specifier/ ~
20:51:16
karlosz
i think its because during the script SB_XC_HOST gets some extra flags by default which are duplicated in slan
20:53:04
Krystof
it doesn't work; it has lisp-land flags --no-sysinit --no-userinit which come before the runtime flag --core
20:53:52
Krystof
so the --no-sysinit implicitly means "we're done with runtime flags", which means that the subsequent --core doesn't get interpreted by the runtime
21:00:47
stassats
i always run with an explicit lisp too, but i never run slam.sh, because it was broken for me too, but differently
21:02:35
karlosz
i suspect that its because ./make.sh autodetects the presence of sbcl and appends the flags to XC_HOST for you
21:05:09
stassats
it takes a minute to rebuild, so i usually avoid dealing with any slam-related problems by just waiting a bit
21:08:08
stassats
i often end up missing some required rebuild and wasting more time because of that
21:10:39
karlosz
we are privileged to have fast machines nowadays; its a good thing that sbcl build times have not increased faster than machines have gotten faster, like most software
21:11:23
stassats
i still use a cpu from 2013, it's about a minute there two, when using multiple threads
21:12:43
karlosz
must be a fast one then. i usually just build single threaded on laptop cpus. I used to try multithreaded builds, but sometimes they would give weird errors