freenode/#clasp - IRC Chatlog
Search
11:02:19
cracauer
out of curiosity, is anybody else using FreeBSD? I want to push the code but would like a second person who it works for.
11:45:08
Selwyn
clasp doesn't seem to recognise the #+ reader macro at times, i get an error "Undefined reader macro for char '#' subchar '+'" while loading a system
11:45:51
Selwyn
i can work around it for now, can provide details for those interested. the confusing thing is that the #+ macro works fine when clasp subsequently drops into the debugger
11:58:47
drmeister
Selwyn: Could you provide an example of where it doesn't recognize the #+ reader macro - that sounds horrifying.
12:00:49
Selwyn
the error occurs while building gsll. the code is naturally full of reader macros not sure why this one failed
12:07:11
Selwyn
https://gitlab.common-lisp.net/antik/gsll/blob/master/linear-algebra/exponential.lisp
13:12:52
Selwyn
great thanks. i am quite optimistic about getting a large subset of GSL running on clasp soon
14:05:56
Selwyn
there is already a port of gsl to lisp called the GSLL which uses cffi. it works in clasp with some minor modifications mostly to the grovellers
15:42:58
Selwyn
in short, whatever SBCL means when it talks about page faults. when I run some diagnostics using GSL on SBCL with (time ...) , it often reports '98 page faults' or something like that. i am told that this is sometimes indicative of poor memory management. i wonder if clasp does the same. this is not a great concern at the moment though.
15:43:53
kpoeck_
regarding the readtable issue, my first bet would be in the form (named-readtables:in-readtable :antik)
15:46:33
Selwyn
https://gitlab.common-lisp.net/ssimsek/gsll/tree/clasp-devel it's not pretty. it requires the clasp-compatible trivial-{features,garbage} libraries, and troublesome read macros have been purged from source code for the time being.
15:52:09
drmeister
Selwyn: There is no equivalent to 'xxx page faults' from SBCL in Clasp. We are currently using the Boehm GC but we will bring the MPS GC back on line soon once I can get around to it.
15:53:06
drmeister
The Boehm GC complains sometimes about repeated large array allocations and very, very rarely it crashes when too much of that happens. For the most part Boehm works fine.
17:30:24
Bike
drmeister: is the static analyzer still broken after the validate-superclass thing id id?
19:36:08
dvssa
drmeister: I saw in the logs a while ago you were having trouble getting cando/clasp (I forget which) building on Linux. Did you manage to fix it?
19:38:31
dvssa
I also seen you've been working on parallelzing the build. What do I need to change in the script you gave me to tell it to build in ||?
19:41:09
dvssa
I was looking at the ELS proceedings as well, it looked like a really interesting event. Petalisp in particular.
19:41:34
drmeister
I just launched a docker build - that's linux - I'll know in an hour if there are problems
20:01:36
dvssa
I just failed with task in '/root/Development/clasp/build/boehm/iclasp-boehm' failed with exit status 1 (run with -v to display more information)
20:02:20
dvssa
Ive built the forkable-boehm, is there not something that needs to be done to make sure when clasp builds it is seen?
20:04:26
drmeister
And clasp needs to link with it - but /usr/local/lib should be in clasp's list of directories to search for libraries.
20:27:58
dvssa
drmeister: I'll get that crash report to you soon, I just nuked where I tried to build from and am downloading everything again but with the internet here in SA it takes a while...
20:49:21
dvssa
So I used the script you gave me, which seemed to behave differently (completed really quickly and in /out/clasp/ theres no /bin folder. The pastebin is from going into clasp and make clean -> make configure -> make.
21:06:22
dvssa
Bike: Well atleast you've spotted it. I'm still in the dark on how clasp gets built so I cant really comment on anything >.<
21:11:45
drmeister
And have you cloned the 'dev' branch of cando - because it's a cando file that is running into problems.
21:26:20
drmeister
Bike: Where does the message "Clang ded" come from? I don't see it in the scraper.
21:26:48
drmeister
I want to catch the error and print the command line that is giving the error. Currently *print-length* is preventing the entire command line from being printed.
21:28:34
Bike
as you can see in the paste, sbcl says there was an error printing the error for some reason
21:29:28
drmeister
8: (CSCRAPE::RUN-CLANG ("/usr/lib/llvm-5.0/bin/clang++" "-E" "-DSCRAPING" "-I./" "-I/usr/lib/llvm-5.0/include" "-fno-omit-frame-pointer" "-mno-omit-leaf-frame-pointer" "-std=c++11" "-flto=thin" "-Wno-macro-redefined" "-Wno-deprecated-register" "-Wno-expansion-to-defined" ...) "/root/Development/clasp/build/boehm/extensions/cando/src/adapt/adaptPackage.sif")
21:30:15
Bike
"Unhandled SIMPLE-ERROR in thread A nested error within --disable-debugger error handling prevents displaying the original error. "
21:52:27
dvssa
I need to drop someone off at the airport now. I probably wont be back again tonight but I'll check the logs if you guys manage to fix something. Cheers
21:52:28
drmeister
dvssa: We don't know right now - we can't debug the problem. I'm on the train - so I'm a bit handicapped at the moment.