Open davidedelvento opened 7 months ago
Following up on this after our offline conversation.
Unfortunately, ninja insists on using fully-qualified paths in its runs, basically defying all my efforts to inject the module-installed eigen3 library (which would require the use of environment-provided settings). This actually is a larger problem, in that it fails to identify and find llvm-lit
and in fact build.ninja
per se includes those as \llvm-lit
and obviously fails with command not found
. I sed that out to simply llvm-lit
and that succeed.
Ninja appears to me to not honoring CPATH, and neither the use of a compiler wrapper which injects the appropriate path itself: even if I rebuild Enzyme with -DLLVM_DIR=/path/to/the/compiler/wrapper/
, all the invocations use /path/to/the/llvm/binary/clang
rather than /path/to/the/compiler/wrapper/clang
as the build systems I am more familiar with do. Even trying to hack my way around this issue (like I have above for llvm-lit) does not work for clang itself, even if I do it on the grand scale of something like find . -name *.script | xargs sed -i.bak s/wrong_llvm_path/right_llvm_path/
And here is the long log of those additional failures not related to eigen3 but to Sparse
Note: there was no /tmp/lit-tmp-76hk8zk6/
from where to harvest ringspring2Dextenddata-0e81a0.cpp
and ringspring2Dextenddata-0e81a0.sh
as hinted in the error message. Probably deleted by the overzealous test-running scripts?
@wsmoses making sure you see this
From the series better late than never, this is a follow up to my previous ticket #1763 (part of the time it took me to respond was that by the time I was ready, new releases of Enzyme and LLVM came out and I did not want to post "noise" with outdated bug reports, so I had to reinstall things from scratch).
The following is with Enzyme
v0.0.103
and LLVMv18.1.1
which I believe are the most current ones.The summary of the failures is
I am not familiar with ninja, so it's a bit hard for me to gather additional relevant information, but I can tell that many of the failures are segmentation faults, and at least 5 are
At least one is
a few more are