freenode/#clasp - IRC Chatlog
Search
18:39:10
cracauer
cclasp" If bclasp is compiled with "cc" or "gcc" on Linux and with "cc" on OSX and FreeBSD that would be a good explanation.
18:47:38
drmeister
Come up with a benchmark that doesn't depend on non-local exits. Like getting the length of a long list.
18:50:08
drmeister
You need to specify what the symbol name will look like for FreeBSD. I can't keep straight who has an underscore prefix and who doesn't
18:54:01
cracauer
I can also boot the machines into each other's OSes. But of course not while they are building.
20:05:18
cracauer
I could never figure out whether these build hangs are caused by a different error that is in the debugger or tries to get into the debugger, or whether the hangs are a build system problem.
20:11:45
cracauer
for the nonlocal exit benchmark above FreeBSD is 6x slower than linux on comparable-ish hardware. I don't think this causes the linux slowness.
20:13:26
cracauer
/usr/src/gnu/usr.bin/gdb/libgdb/../../../../contrib/gdb/gdb/solib-svr4.c:1444: internal-error: legacy_fetch_link_map_offsets called without legacy link_map support enabled.
20:39:16
cracauer
I also have the problem that with a llvm9 I compiled myself, I get those missing symbols when linking, but only for the Clasp build. It picks up standard C++ headers from the OS, when I want to link against the llvm library. But I have -I/opt/clasp-support statements in wscript.config. And the c++ compilation works as intended for small test programs.