freenode/#clasp - IRC Chatlog
Search
11:35:15
drmeister
I have some folks who want to install on macOS and it would be good to simplify the instructions.
11:36:22
drmeister
stassats: You make a very good point. I just need to point the build system at the brew installed llvm-config.
11:37:10
drmeister
I was thinking that I wouldn't have externals-clasp installed in that account - but I can ensure that it isn't used in my account by changing the wscript.config.
12:10:14
drmeister
::notify attila_lendvai I made a change to the parallel scraping code - so that it always does 8 parallel scraping jobs. It looks like every time we pass a different -j xx argument to ./waf it starts scraping everything all over again. My compromise hack is to stop that from happening. We need a better way
12:11:36
drmeister
::notify balrog - right you said that we would need to also link in libffi - digging deeper.
12:17:55
drmeister
::notify balrog I'm going to add libffi as a dependency on macOS if we can build clasp with brew llvm@5
12:51:26
drmeister
Argh - in waf you name the library FFI and then you append to LIB "LIB_FFI" to get it to link - otherwise it silently fails.
13:05:21
drmeister
::notify balrog I can now build and link iclasp-boehm on macOS after brew install llvm@5 libffi - thank you so much for your advance work on this.
13:05:50
Colleen
balrog: drmeister said 54 minutes, 14 seconds ago: - right you said that we would need to also link in libffi - digging deeper.
13:05:50
Colleen
balrog: drmeister said 47 minutes, 55 seconds ago: I'm going to add libffi as a dependency on macOS if we can build clasp with brew llvm@5
13:05:50
Colleen
balrog: drmeister said 29 seconds ago: I can now build and link iclasp-boehm on macOS after brew install llvm@5 libffi - thank you so much for your advance work on this.
13:06:26
balrog
The problem with adding libffi as a dependency is that if someone has compiled their own LLVM without libffi, that will lead to problems
13:07:25
balrog
https://github.com/llvm-mirror/llvm/blob/76b46df975a33d6a5ce0c606f09dfa88e195d243/tools/llvm-config/llvm-config.cpp#L702
13:07:57
balrog
It’s an llvm-config issue that’s been known since that source code FIXME was added, a long time ago.
13:08:48
balrog
The only way to programmatically find out if it’s needed is using otool to check if the lib is linked against libffi. Or maybe compile and attempt to run a test program (that’s the autotools way right?)
13:11:11
drmeister
waf does run a test build with each library - but this is a bit different - we want to build a test file linking llvm and if it fails, add libffi as a dependency?
13:13:15
balrog
I’m not sure if there’s a specific lib you have to link in — when I checked with otool it seemed the main llvm lib needed libffi
13:21:33
drmeister
I couldn't run the tests that I wanted last night because I didn't have your modified sicl
13:24:21
Bike
yeah what's with that? all power goes off for five seconds some time in the next eight hours?
13:28:21
drmeister
I am too much of a molecular biologist at heart - molecular biology is all about suppressors of suppressors of suppressors.
13:29:40
Bike
well it would make more sense if we did have some map kinase kinase kinase kinase floating around but in this case there's only one level
13:38:34
balrog
drmeister: otool -L /usr/local/opt/llvm@5/lib/libLLVM.dylib: (blah...) /usr/local/opt/libffi/lib/libffi.6.dylib (compatibility version 7.0.0, current version 7.4.0) (...blah)
13:40:07
balrog
just compiling a test program and linkiung the lib isn't enough, though. let me dig a bit deeper
13:44:07
balrog
(btw unrelated/offtopic, I read "Ignition" by John Clark over the past week, it's ... a pretty fun read)