[all-commits] [llvm/llvm-project] 167b50: [libcxx][ci] In picolib build, ask clang for the n...

David Spickett via All-commits all-commits at lists.llvm.org
Wed May 1 07:10:24 PDT 2024


  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: 167b50669c03ad888bf2f00c61424bedac43a050
      https://github.com/llvm/llvm-project/commit/167b50669c03ad888bf2f00c61424bedac43a050
  Author: David Spickett <david.spickett at linaro.org>
  Date:   2024-05-01 (Wed, 01 May 2024)

  Changed paths:
    M libcxx/utils/ci/run-buildbot

  Log Message:
  -----------
  [libcxx][ci] In picolib build, ask clang for the normalised triple (#90722)

This is needed for a workaround to make sure the link later succeeds. I
don't know the reason for that but it is definitely needed.

https://github.com/llvm/llvm-project/pull/89234 will/wants to correct
the triple normalisation for -none- and this means that clang prior to
19, and clang 19 and above will have different answers and therefore
different library paths.

I don't want to bootstrap a clang just for libcxx CI, or require that
anyone building for Arm do the same, so ask the compiler what the triple
should be.

This will be compatible with 17 and 19 when we do update to that
version.

I'm assuming $CC is what anyone locally would set to override the
compiler, and `cc` is the binary name in our CI containers. It's not
perfect but it should cover most use cases.



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications


More information about the All-commits mailing list