freenode/#clasp - IRC Chatlog
Search
23:06:20
kpoeck_
drmeister: how did you solve the "assert waf_node != None, "Could not find waf node for lisp file %s - did you run './waf update_dependencies'?" % file_name" probelm
23:12:47
kpoeck_
assert waf_node != None, "Could not find waf node for lisp file %s - did you run './waf update_dependencies'?" % path
23:13:24
kpoeck_
with this correction I seem to be missing src/lisp/kernel/contrib/alexandria/package
23:14:11
drmeister
kpoeck_: You might need to delete your copy of sicl and let ./waf configure get you a new one
23:15:11
drmeister
I didn't quite do that because I thrashed around for a bit and then Bike set us up with a new commit to draw from.
23:16:19
drmeister
But I'm not sure what happens when you have a separate branch for 6 months and then merge it and then try to build with inconsistent repos within your repo
23:18:29
balrog
drmeister: we'll probably need -lffi when building against distro-packaged libllvm on Ubuntu and Arch as well.
23:22:22
drmeister
It is an upstream problem right? We should get snooty like the rust folks. I don't want to be out snootied.
23:29:59
kpoeck_
AssertionError: Could not find waf node for lisp file src/lisp/kernel/contrib/Eclector/code/readtable/packages - did you run './waf update_dependencies'?
23:31:30
Bike
i mentioned to you that it would build eclector and alexandria and stuff even with generate-ast
23:32:22
drmeister
kpoeck_: Give me a few minutes to sort out what is going on and what we are missing.
23:32:26
Bike
https://github.com/clasp-developers/clasp/commit/bd04d3ec093826ea8e38ef69dde94234614137c4
23:32:46
Bike
https://github.com/clasp-developers/clasp/commit/bd04d3ec093826ea8e38ef69dde94234614137c4#diff-dc6134e3d3c869a052520d86f46371dcL156 here specifically
23:33:11
kpoeck_
Its compiling, I think we just miss to pull alexandria and eclector in update_dependencies
23:34:46
drmeister
I did a quick ediff on the dev wscript file and the changes I made today and wiped out the code to pull those two repos - fixing...
23:37:55
drmeister
Swinging between panic that I broke peoples builds and elation that we got the merge working and stuff is working in the lab.
23:39:24
drmeister
I would have caught this problem if I hadn't pulled the merge into my cst-dev directory, which had a recent enough Eclector and alexandria in it already.
23:42:48
drmeister
I know - I'm tucking into some fresh kiwi fruit - confirmation that I don't live in the worst of all worlds.
23:43:51
kpoeck_
There are people in the company that I work for, that still have to use cobol on a mainframe :-)
23:48:52
karlosz
drmeister: do you have timings for clasp self compiling cleavir? i wanted to compare my self host time with clasps but it up all my ram again
0:24:25
balrog
drmeister: looks like Ubuntu doesn't package the Clang libs in a way that clasp's wscript expects
0:26:54
drmeister
Because on supercomputers I need static linking - so I started from there and never changed it.
0:29:29
drmeister
We can switch to dynamic linking - but waf seems to want one or the other. Take a look at the wscript where it searches for the boehm library. It tries first to find a static version and then it drops down to the dynamic version.
0:30:33
drmeister
balrog: I don't want to touch another build system until we have loads of developers and there is a really, really, really good reason.
0:31:48
balrog
this would not be the only project I've had to deal with that uses a fairly uncommon build system. :|
0:33:07
drmeister
It's python - I understand python. I don't understand cmake or autotools and I despise boost::build and perforce jam.
0:34:29
balrog
the other build system I'm citing above is a fork of Premake and interestingly enough, uses Lua
0:37:21
drmeister
It's Python and you have function calls to build a dependency graph. We don't use waf the way it was intended - or we barely do.
0:37:59
drmeister
I know a guy who left his job partly because he hated the build system that they decided to switch to.
0:38:35
balrog
I know multiple people who wrote their own build systems because either they hated everything that existed or everything that existed was unsuitable for the application.
0:39:02
drmeister
Two? Three? years ago I switched to waf with no idea how it would go because I was so frustrated with boost::build.
0:39:38
balrog
I've used scons before (also python) and my opinion on it is that it's clean and workable bu tit doesn't scale.
0:40:02
drmeister
All I ever hear is programmers vowing that they are going to develop their own build system.
0:40:38
drmeister
Ha! Where they should really be focusing their efforts is to develop their own compiler.
0:42:16
balrog
haha funny you should say that. one of them is developing FPGA tools, another is developing cross platform compatibility environments to run legacy Apple/Mac software on modern platforms, as well as Unix-like environment on legacy platforms
0:45:54
balrog
just like the effort to improve workflows for computational chemistry led to building a Common Lisp compiler
0:48:58
balrog
my experience with scons? it couldn't handle macOS "fat binaries", it couldn't handle cross compiling
5:42:02
drmeister
::notify Bike In the new dev - can you give me a switch where I can compile with cst but not inlining? I need to debug %defcallback because just as I suspected - when I try to compile cando with the new dev it fails in the worst place possible. While compiling the pzmq system. Source tracking could help me debug it.
5:53:41
drmeister
::notify Bike What happened to compile-lambda-form-to-llvm-function? I need it to make defcallback work - can revivify it https://github.com/clasp-developers/clasp/blob/mps/src/lisp/kernel/cleavir/translate.lisp#L1176
10:05:05
Colleen
attila_lendvai: drmeister said at 2018.06.12 21:30:28: I ran into the problem you saw on linux "error: can't create dynamic relocation R_X86_64_PC32 against symbol:" - I'm trying to figure out a work around. Can stuff just keep working?
10:05:05
Colleen
attila_lendvai: drmeister said at 2018.06.12 21:57:09: It looks like a workaround is to not use the lld linker when building in object mode on linux (phew). I added support for lld for bitcode/lto mode - so it's no big deal to switch back to ld for object mode.
10:05:06
Colleen
attila_lendvai: drmeister said 21 hours, 54 minutes ago: 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
10:39:58
attila_lendvai
::notify drmeister hrm, I could reproduce the waf jobs issue locally. a note: it's better to record the reason for the change right into the wscript file in a comment. I've seen that diff long ago, versus just saw this ephemeral note here on irc. code comments also remain near the change for long if someone later on wonders about it. I've pushed a commit to record it there.
10:43:11
attila_lendvai
::notify drmeister re that linker issue: reading the bug reports it look to me a legit error that happens due to not doing something properly, and it may not cause any issues when linking in a more permissive environment (macos?). but it's just a vague impression...
10:47:15
Colleen
drmeister: attila_lendvai said 7 minutes, 17 seconds ago: hrm, I could reproduce the waf jobs issue locally. a note: it's better to record the reason for the change right into the wscript file in a comment. I've seen that diff long ago, versus just saw this ephemeral note here on irc. code comments also remain near the change for long if someone later on wonders about it. I've pushed a commit to record it there.
10:47:15
Colleen
drmeister: attila_lendvai said 4 minutes, 4 seconds ago: re that linker issue: reading the bug reports it look to me a legit error that happens due to not doing something properly, and it may not cause any issues when linking in a more permissive environment (macos?). but it's just a vague impression...