Search
Thursday, 8th of November 2018, 16:45:12 UTC
16:50:05
joshe
asarch: you're probably running sbcl from a partition which isn't mounted wxallowed
16:57:59
asarch
Well, the source code is at /home/asarch/bin/sbcl-1.4.13 and I am using this command to build it: ./make.sh --fancy --prefix=$HOME/bin/sbcl
16:58:46
joshe
sbcl won't run unless the filesystem it's on is mounted with the "wxallowed" flag, and sbcl runs itself from the source directory during the target-1 build step
16:59:10
stassats
installing to $HOME too
16:59:36
joshe
you'll need to move the source to a partition which is mounted with that option, like /usr/local, or update the mount options for /home to add it
17:01:04
joshe
(until someone rewrites sbcl to never map W|X pages, but don't hold your breath)
17:01:23
joshe
because https://undeadly.org/cgi?action=article&sid=20160527203200
17:02:40
joshe
np, it's far from obvious
17:09:45
stassats
joshe: can we detect that?
17:09:59
stassats
and i just hosed my virtualbox
18:26:53
joshe
neat, I like the new (?) host-2 output
18:27:34
stassats
i don't, but not for technical reasons
18:27:48
stassats
i'm just so used to the old output
19:02:52
Xof
I used to like the one-line-per-toplevel-form output
19:03:14
Xof
it actually let me do insane remote debugging. But oh, was it noisy
19:09:01
joshe
ACTION tries to remember how to commit
19:09:59
stassats
you don't need to update version.lisp-expr
19:17:38
joshe
anyway, you'll now get an error in make-config if you try to build without wxallowed
21:50:47
fiddlerwoaroof
This W^X stuff seems like a really C-centric view of programming
21:55:24
fiddlerwoaroof
I'm not sure, but it seems like it assumes that the languages being used aren't very good at ensuring memory safety
21:56:11
stassats
and probably any other language
22:04:40
joshe
I think openbsd will stop adding OS-level mitigations for C buffer overflows when they stop happening
22:05:08
joshe
or when they stop allowing remote code execution
Friday, 9th of November 2018, 4:45:12 UTC