On Mon, 1 Jul 2024 at 14:56, David Spickett david.spickett@linaro.org wrote:
This is one for @Omair Javaid omair.javaid@linaro.org who is on bots this week.
But to save him some confusion, I noticed that the next build https://lab.llvm.org/buildbot/#/builders/122/builds/151 passes. This is because https://github.com/llvm/llvm-project/commit/038bc1c18c786e14cc306401b0014426... required lld which surprisingly, makes the test unsupported?
UNSUPPORTED: Profile-armhf :: Linux/instrprof-vtable-value-prof.cpp (74341 of 77518)
Which is odd because it's enabled in both stages and used to link in stage 2.
I am guessing behavior is intended as LLVM_ENABLE_LLD=ON is not setting CLANG_DEFAULT_LINKER for stage 2. Should we expect clang to use just built lld in stage 2 by default without even setting CLANG_DEFAULT_LINKER?
Did you get any other notifications of the same include issue, particularly from Linaro's other builders?
On Mon, 1 Jul 2024 at 10:39, mingmingl minglotus6@gmail.com wrote:
Greetings! This is Mingming and I'm an LLVM contributor. I have received a lot of useful code review feedback from aarch64 experts. Thank you for all of that!
I'm writing to report a failure ( https://lab.llvm.org/buildbot/#/builders/122/builds/150) on buildbot clang-armv8-lld-2stage triggered by my recent patch. The issue seems to stem from the C++ standard libraries not being configured in the buildbot environment.
While using a c-style header is a workaround (which pr 97245 https://github.com/llvm/llvm-project/pull/97245 did), @petrhosek reminded me that it would be good to inform maintainers so they can take a look, which makes sense to me.
Could someone please assist in resolving this configuration problem? Thank you in advance and let me know if I miss anything.
Thanks, Mingming _______________________________________________ linaro-toolchain mailing list -- linaro-toolchain@lists.linaro.org To unsubscribe send an email to linaro-toolchain-leave@lists.linaro.org