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

apple llvm 19.1.6 missing libclang_rt.asan_ios_dynamic.dylib #120362

Open
calvin2021y opened this issue Dec 18, 2024 · 2 comments
Open

apple llvm 19.1.6 missing libclang_rt.asan_ios_dynamic.dylib #120362

calvin2021y opened this issue Dec 18, 2024 · 2 comments

Comments

@calvin2021y
Copy link

I try download https://github.com/llvm/llvm-project/releases/download/llvmorg-19.1.6/LLVM-19.1.6-macOS-ARM64.tar.xz, compare to llvm18 there is no libclang_rt.asan_ios_dynamic.dylib

I try build myself on x86_64, not work with error:

file Parser.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file TableGenBackendSkeleton.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file DetailedRecordsBackend.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file TGLexer.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file TableGenBackend.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file TGParser.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file StringMatcher.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file SetTheory.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file JSONBackend.cpp.o differs between phase 2 and phase 3
sed: RE error: illegal byte sequence
sed: RE error: illegal byte sequence
file Error.cpp.o differs between phase 2 and phase 3
# Packaging the release as clang+llvm-19.1.6-x86_64-apple-darwin22.tar.xz

try build with:

llvm/utils/release/test-release.sh \
  -release 19.1.6 \
  -final \
  -triple x86_64-apple-darwin22 \
  -j 12 \
  -use-ninja \
  -configure-flags  "-DLLVM_USE_STATIC_ZSTD=ON" \
  -lldb \
  -no-test-suite 
@calvin2021y
Copy link
Author

linux build also failed:

llvm/utils/release/test-release.sh \
  -release 19.1.6 \
  -final \
  -triple x86_64-unknown-linux-gnu \
  -j 32 \
  -use-ninja \
  -configure-flags  "-DLLVM_USE_STATIC_ZSTD=ON" \
  -lldb -no-test-suite 
``

@calvin2021y
Copy link
Author

calvin2021y commented Dec 18, 2024

macOS arm build failed after take almost 1 day(macOS 15.2):

llvm/utils/release/test-release.sh \
  -release 19.1.6 \
  -final \
  -triple arm64-apple-darwin24.2.0 \
  -j 8 \
  -use-ninja \
  -configure-flags  "-DLLVM_USE_STATIC_ZSTD=ON" \
  -lldb -no-test-suite 

Undefined symbols for architecture arm64:
  "___divdc3", referenced from:
      ___kmpc_atomic_cmplx8_div in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx8_div in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cmplx8 in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cmplx8 in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx8_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx8_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx10_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx10_div_cpt in kmp_atomic.cpp.o
      ...
  "___divsc3", referenced from:
      ___kmpc_atomic_cmplx4_div in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cpt in kmp_atomic.cpp.o
      ___kmpc_atomic_cmplx4_div_cpt in kmp_atomic.cpp.o

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

No branches or pull requests

2 participants