Jerry Ling
Jerry Ling
I now suspect it's because the `LLVM` building step does not respect the `CMAKE_TOOLCHAIN_FILE` BinaryBuilder.jl set: ``` cmake -Dpyroot=OFF -DCMAKE_INSTALL_PREFIX=$prefix -DCMAKE_TOOLCHAIN_FILE=${CMAKE_TARGET_TOOLCHAIN} -DCMAKE_BUILD_TYPE=Release ../root-6.28.08 ``` is there a way to verify...
https://buildkite.com/julialang/yggdrasil/builds/6619#018bcea7-4b07-476a-9c1a-fccfb081f038/6-1790 removing TOOLCHAIN files doesn't work but got us much further.
>If you need to build LLVM then i would look at the LLVM build we have to see what things need to be done I don't understand the fix we...
on 6.26 `LLVMSupport` does not build :(
ok with `julia build_tarballs.jl --debug` I have error log: src/NATIVE/CMakeFiles/CMakeOutput.log ``` The system is: Linux - 6.6.2-arch1-1 - x86_64 Compiling the C compiler identification source file "CMakeCCompilerId.c" succeeded. Compiler: /opt/bin/x86_64-linux-gnu-libgfortran5-cxx11/x86_64-linux-gnu-gcc...
(I have invited you to my fork and also updated the current content with your fork's content)
>I am not aware that ROOT supports cross-compilation. That might be a problem... now I wonder if ROOT can build on Alpine linux to begin with, ignore cross-compilation for a...
don't think so -- I think it's better now, haven't tested in SR.jl could try just Tuple?
this particular can be done via package extension?
I thought that was your initial point, that we shouldn't have a separate eval_scalar, just accept static array and be efficient