Search
19:16:09
stassats
easier just to get new sources
19:22:20
alaa
I did that. I removed the quicklisp folder and quickload again Esrap and Clx but the same error
19:22:52
alaa
is there a service to share the output. I do not want to paste the output here
19:31:51
alaa
I also now suspect something is not working with my setup. I'm now creating a new virtualbox to check a clean setup
19:31:58
alaa
for Esrap: https://gist.github.com/alaa-alawi/2f420e7070105bcf32a311dedbb7f49c
19:32:12
alaa
for Clx: https://gist.github.com/alaa-alawi/2617129591dba8f236a27c809cbdd671
19:32:24
alaa
for hunchentoot: https://gist.github.com/alaa-alawi/0dde0f5d981d56a9157d43d437e93a2c
19:33:15
stassats
how did /bin/sh even get there
19:34:36
stassats
ok, i think you have a rogue reader macro
19:34:53
stassats
alaa: what does (get-dispatch-macro-character #\# #\!) say
19:35:53
stassats
or rather just !, right
19:36:05
stassats
(get-macro-character #\!)
19:36:43
alaa
(get-dispatch-macro-character #\# #\!) -> nil
19:37:12
alaa
oops: (get-macro-character #\!) -> SHELL-CODE
19:38:02
|3b|
ACTION wonders if that managed to actually run anything in shell while compiling things
19:39:59
alaa
thanks a lot! this is exactly shooting oneself in the foot :)
19:42:39
alaa
may I ask, how did you deduce that it was the reader specifically the #\!
19:42:58
alaa
I kept jumping between both the source and error msg without luck
19:42:59
|3b|
looking at the correct source and the error
19:43:46
|3b|
the (:export ... #:character-ranges) form in the error didn't match the source, and changed at the #:!
19:44:20
|3b|
so looking at the clx source, the form in the error also contained some symbols with ! in them
19:45:46
|3b|
(possibly combined with some vague memory of people using ! as a reader macro for running things in sh)
19:46:49
alaa
thanks! this is really helpful