Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sat, 30 Oct 2021 00:25:54 -0400
From: Jeffrey Walton <>
Subject: Re: Failed to build musl 1.2.2 by using clang cross compiler

On Fri, Oct 29, 2021 at 11:46 PM Chunlin Zhu <> wrote:

> Hello,
> On my computer I have built and install the llvm toolchain from the source
> code by using the below configuration, the llvm lib is installed in the
> /usr/local/lib folder.
> *cmake -S llvm -B build -G "Unix Makefiles"
> -DLLVM_ENABLE_PROJECTS="clang;clang-tools-extra;libcxx;libcxxabi;compiler-rt;lld"
> And I am trying to build musl libc 1.2.2 for aarch64 by using llvm/clang,
> and I use the below configure:
> *./configure CC=clang --target=aarch64 CFLAGS="-v --target=aarch64
> --rtlib=compiler-rt" AR=/usr/local/bin/llvm-ar
> RANLIB=/usr/local/bin/llvm-ranlib LIBCC=-lcompiler_rt
> --syslibdir=/usr/local/lib*
> It report the error as below:
> And I find the compile phase is OK, the problem occurs during the link
> phase, I don't understand why finally gcc is invoked.
> By the way, the below configure works on my computer:
> ./configure CC=clang
> make -j4

Set LD to clang, too. It sounds like GCC is creeping in because it is a

For the link error with --noexecstack, the linker needs -z,noexecstack. So
add -Wl,-z,noexecstack to LDFLAGS. See the ld(1) man page at

ASFLAGS should continue to use --noexecstack.


Content of type "text/html" skipped

Download attachment "image.png" of type "image/png" (236690 bytes)

Download attachment "image.png" of type "image/png" (15169 bytes)

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.