Search
Monday, 18th of September 2017, 18:19:19 UTC
18:27:34
_rumbler31
Bike: what did you read to resolve the order that the methods are resolved?
18:28:51
specbot
Standard Method Combination: http://www.lispworks.com/reference/HyperSpec/Body/07_ffb.htm
19:23:10
Fare
some-user: probably is. I need to send the rushes to Arthur G...
19:54:34
francogrex
i remember that some people were "working" still on paul dietz's ansi tests (refining etc). do you know whether it's true or had i imagined it?
19:56:45
Bike
https://gitlab.common-lisp.net/ansi-test/ansi-test/commits/master judge for yourself
19:58:25
francogrex
well well... good to know!
20:07:21
phoe
A question about STATIC-VECTORS. What is the idiomatic way of copying a Lisp vector of uint8 into a static vector?
20:07:40
phoe
Preferably in form of (with-static-vector-from-lisp-vector (v *vector*) ...)
20:07:47
phoe
where *vector* is a Lisp vector.
20:08:08
phoe
Oh wait, I can supply INITIAL-CONTENTS to MAKE-STATIC-VECTOR.
20:15:14
phoe
Why does MAKE-STATIC-VECTOR have :INITIAL-CONTENTS but WITH-STATIC-VECTOR does not?
20:22:09
|3b|
ACTION usually just uses replace
0:03:52
incal
I'm trying to get started with SDL2 and CL with SBCL, after loading the components with quicklisp it says I should run an example like this, (sdl2-examples:basic-test), however the debugger says "debugger invoked on a BORDEAUX-THREADS::BORDEAUX-MP-CONDITION:
0:03:52
incal
There is no thread support in this instance." - I Googled it and it doesn't seem to be too closely connected to SDL (?)
0:05:45
Bike
sounds like your sbcl was built without thread support
0:05:50
Bike
which you might need for SDL
0:06:18
incal
is there some other implementation you know of that handles this out of the box?
0:06:33
Bike
sbcl does, it just has to be the right box.
0:06:54
incal
let's check out the repos again...
0:07:00
Bike
did you build sbcl yourself?
0:08:06
incal
no, I got it from the repos. There is pack I don't have tho that sounds interesting, cl-clx-sbcl, "X11 CL client lib for SBCL"
0:08:19
Bike
probably don't need that for SDL
0:08:37
Bike
if your repo isn't cooperative, maybe try CCL? it might be built properly
0:08:45
incal
ok there is only one sbcl, let's hear what they say
0:09:29
incal
version "SBCL 1.2.4.debian"
0:11:05
|3b|
that's pretty old, it isn't too hard to build sbcl from source, then you get threads and a current version
0:11:37
Petit_Dejeuner
incal: Using a package manager?
0:12:03
incal
Raspbian, Debian fork
0:12:15
|3b|
linux distro packages tend to be a bad idea in general though, not enough lisp users to get well-maintained packages into distros :(
0:12:42
incal
ok, so compile SBCL manually?
0:13:19
|3b|
yeah, keep your distro version for now (to use for manual build)
0:13:31
Petit_Dejeuner
|3b|: Majority of new stuff seems to be done through language specific package managers pip/gems/quicklisp. It's kind of a pain.
0:13:43
Petit_Dejeuner
I guess it's better than everything getting updated always every time.
0:14:14
|3b|
actually, raspbian is arm, isn't it? 32 bit?
0:14:29
|3b|
ACTION isn't sure arm sbcl has thread support
0:14:58
Petit_Dejeuner
ACTION thinks he had to go through all this once several years ago.
0:15:27
Petit_Dejeuner
I ended up installing some lisp from source because I couldn't get others to work or others wouldn't support arm.
0:15:46
|3b|
yeah, i think sbcl only supports threads on arm for 64bit, not 32
0:16:17
incal
OK, well "good news" anyway, that explains it
0:16:32
|3b|
so building sbcl from source won't help with that part, though i'd argue sdl2 should work without it anyway
0:16:50
Petit_Dejeuner
'64 bit arm' Weird, I thought regular arm was 32 bit isntructions and 16 bit half words with the thumb extension.
0:17:07
Petit_Dejeuner
I'm stuck in the past.
0:17:35
|3b|
yeah, they added a 64bit version at some point
0:18:09
|3b|
if it is armv7, you could try ccl https://ccl.clozure.com/manual/chapter2.2.html#obtaining-ccl
0:19:45
incal
OK I try: ccl-1.7-linuxarm.tar.gz
0:24:15
incal
"CPU doesn't support required features"
0:25:43
incal
man, why does it have to be so complicated? maybe sdl2 on an R-Pi is a bad idea to begin with...
0:27:43
|3b|
probably not a horrible idea, but might take a bit more work than an x8664 system, and not sure about performance
0:29:18
incal
I just want to draw boxes and move sprites around a canvas
0:29:26
|3b|
hmm, looks like that might have a 64bit cpu
0:30:02
incal
Linux raspberrypi 4.9.35-v7+ #1014 SMP Fri Jun 30 14:47:43 BST 2017 armv7l GNU/Linux
0:31:04
|3b|
try grabbing the arm64 binary from http://www.sbcl.org/platform-table.html and see if it runs
0:32:28
|3b|
untar it, then in the directory that creates, ./run-sbcl.sh
0:35:41
incal
(running SBCL from: .)
0:35:41
incal
./src/runtime/sbcl: 2: ./src/runtime/sbcl: Syntax error: word unexpected (expecting ")")
0:35:55
incal
there is an install.sh script tho?
0:36:19
|3b|
don't run the install script unless it works :)
0:36:29
|3b|
that was from running run-sbcl.sh ?
0:36:59
|3b|
ok, guess that idea won't work either :(
0:37:54
|3b|
so remaining options are try ecl, or fix cl-sdl2 to not need threads
0:38:50
incal
OK, I need a break after all setbacks, then I'll try ecl
0:38:57
incal
thanks for the efforts
1:33:49
abel-abel
iqubic: Maybe it's midnight in your timezone?
1:34:41
iqubic
It is always morning when a new person logs on.
1:34:50
iqubic
It the global irc time zone
1:35:30
iqubic
Since irc is used all over the work
1:35:45
iqubic
world timezones are pointless here.
1:44:38
aeth
good 2017-09-19T01:44Z
1:47:23
aeth
the reader can assign their own meaning to the unambiguous facts
2:06:40
incal
ecl which is version 13.5.1 cannot load quicklisp, /usr/bin/ld: cannot find -lffi
2:06:40
incal
collect2: error: ld returned 1 exit status
2:06:40
incal
Condition of type: SIMPLE-ERROR
2:06:43
incal
Error code 1 when executing
2:06:46
incal
(RUN-PROGRAM "gcc" ("-o" "/home/incal/.cache/common-lisp/ecl-13.5.1-unknown-linux-arm/home/incal/quicklisp/quicklisp/package-ASDF-TMP.fas" ...))
2:07:13
incal
I don't know if you need quicklisp for sdl2? but they say in the documentation it is the "easiest way"... well
2:13:14
pjb
incal: ecl is at version 16.1.2 at least.
3:08:44
specbot
http://www.lispworks.com/reference/HyperSpec/Body/s_flet_.htm
3:50:08
specbot
http://www.lispworks.com/reference/HyperSpec/Body/t_intege.htm
4:18:59
iqubic
Are there any lisp WMs out there?
4:20:33
iqubic
As in, can be configured in lisp.
4:21:53
iqubic
What do you configure it with? What language do you use?
4:22:11
aeth
It is entirely written in Common Lisp
4:22:21
iqubic
And how does that interact with the hardware? Through X?
4:22:42
aeth
Iirc, X is based on a client/server model (which is why you can e.g. ssh -X)
4:22:55
aeth
So there is an X client written in CL
4:24:12
iqubic
Yeah, that is what I want. Got a link to that X client in CL?
4:24:18
jasom
clx is written entirely in CL
4:24:35
aeth
https://github.com/sharplispers/clx
4:24:45
aeth
And this is stumpwm. https://github.com/stumpwm/stumpwm
4:24:57
jasom
now we just need an X server written entirely in CL; any takers?
4:27:16
loke
And then you have McCLIM that is a UI sytem built on CLX
4:27:27
loke
iqubic: Isn't it exwm?
4:27:49
iqubic
loke: blame autocorrect.
4:27:51
aeth
Most graphical CL applications do not use clx, though. qt, tk, and sdl are popular.
4:28:14
iqubic
I need to learn about graphical CL lobs.
4:28:54
iqubic
I officially hate apple's autocorrect jow.
4:29:05
aeth
I was talking to a Lisper who used Lisp back in the day and he used tk, so I guess some things never change.
4:29:42
loke
iqubic: You are IRC'ing from a phone?
4:29:55
loke
And an Iphone no less.
4:30:35
iqubic
My laptop is in the shop for repair. So I have to use this until I can find time to get Linux onto my old desktop.
4:31:04
iqubic
Currently it will not boot at all. It needs a new hard drive and then it will work
5:09:39
beach
Good morning everyone!
5:38:25
neoncont_
** NICK neoncontrails
Tuesday, 19th of September 2017, 6:19:19 UTC