Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

libc: use runtimes dir as base for cmake #342

Merged
merged 2 commits into from
Dec 12, 2024

Conversation

nickdesaulniers
Copy link
Member

Fixes: #325

@nickdesaulniers nickdesaulniers merged commit c9fcbe4 into llvm:main Dec 12, 2024
2 checks passed
@nickdesaulniers nickdesaulniers deleted the runtimes_dir branch December 12, 2024 22:03
nickdesaulniers added a commit that referenced this pull request Dec 12, 2024
nickdesaulniers added a commit that referenced this pull request Dec 12, 2024
maybe old version of python is being used???

Fixes: #342
nickdesaulniers added a commit that referenced this pull request Dec 12, 2024
@nickdesaulniers
Copy link
Member Author

@mikhailramalho can you please rm -rf * the contents of the libc-riscv32-qemu-yocto-fullbuild-dbg buildbot's build dir? The cmakecache is stale again as a result of this change.

@mikhailramalho
Copy link
Member

Done, cmake is passing now but running the tests is failing: https://lab.llvm.org/buildbot/#/builders/196/builds/2315/steps/4/logs/stdio

Did the path to the tests change? rsync seems to be confused now

@nickdesaulniers
Copy link
Member Author

Did the path to the tests change?

Maybe. I guess I'm surprised to see rsync involved; I would guess that's specific to the libc-riscv32-qemu-yocto-fullbuild-dbg buildbot? Can you reset rsync on the receiving end then if the paths for the tests did change? Perhaps that's necessary for the buildbot whenever resetting the cmake cache?


I'm also curious about the contents of /home/libcrv32buildbot/cross.sh. Is that the massive command line invocation for qemu? Looks like you set that script for -DCMAKE_CROSSCOMPILING_EMULATOR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants