similar to: [Bug 10715] New: IPv6 configure test fails on musl c-library

Hello there, I'm building a Linux distribution based on musl and LLVM as default toolchain (including lld/libc++/libc++abi/libunwind rather than GNU). For most of the time this works pretty well. However I'm having troubles with few packages, webkit for instance fails because of max_align_t being redeclared in musl's stddef.h I see that stddef.h is provided by both musl and in the

> ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for > ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl > (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a > MIT licensed, highly POSIX compliant library offering high performance and a > small foot print. I spent several weeks evaluating musl before deciding to use

> Hello, > > I wanted to ask if there's a reason efi/wrapper.{h,c} use __uint*_t > instead of including stdint.h and using the therein defined uint*_t > types? This breaks compilation of the efi blobs on systems with the musl > libc since that doesn't define __uint*_t types. > > -- > Simon Thelen FWIW... As a simple quick basic test, I took the efi32

Here is tests/reg-tests-1c.Rout.fail - http://pastebin.com/raw/3QVDUBwT About the libm, I don't know which one R uses. musl has its on libm. http://git.musl-libc.org/cgit/musl/tree/src/math I think I also have openlibm installed, but I don't think that's used. Any more information I can give to help debug this? Thanks. On Mon, Feb 1, 2016 at 3:49 PM, Martin Maechler <maechler

I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and lld (under `tools` directory) and libunwind, compiler-rt, libcxx and libcxxabi (under `projects` directory). All are the latest versions cloned from GitHub mirror, branch `master`. I'm trying to configure with the following options: CLANG_DEFAULT_CXX_STDLIB = libc++ CLANG_DEFAULT_RTLIB = compiler-rt

There is incompatibility between R strptime and musl libc. I posted about it on their mailing list, but they need more information I can't provide, so I'm forwarding the message here in hope R developers can help. Thanks. ---------- Forwarded message ---------- From: Rich Felker <dalias at libc.org> Date: Thu, Feb 4, 2016 at 2:07 PM Subject: Re: [musl] strptime() question To: Alba

Le 25/03/2019 à 14:41, Peter Smith a écrit : > Hello David, > > I don't know much about the specifics of Musl, so I'm responding generally. > > As I understand it, clang expects to find the compiler-rt libraries > relative to the resource directory, which you can find out the > location of with clang --print-resource-dir . By default it is > lib/clang/9.0.0

I'm trying to compile LLVM with musl libc library. The compilation process fails on the following: x86_64-linux-musl-g++ -DGTEST_HAS_RTTI=0 -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -Ilib/Support -I../lib/Support -Iinclude -I../include -fPIC -fvisibility-inlines-hidden -Werror=date-time -std=c++11 -Wall -W -Wno-unused-parameter

I have managed to compile llvm and clang against musl, but it behaves really strange: At first I tried to launch the compiler with musl dynamic loader: $ LD_LIBRARY_PATH=/path/to/musl/lib /path/to/musl/lib/ld-musl-x86_64.so.1 /path/to/llvm/bin/clang -v clang version 4.0.0 (https://github.com/llvm-mirror/clang 40adebeca0f99006d407508653c2cbd270a1a51c) (https://github.com/llvm-mirror/llvm

Hello, I'm trying to create a pure LLVM toolchain (that will not depend on GNU and produce GNU-free code too) on a musl based distribution. For now, I use gcc to bootstrap and build all LLVM components. I do it individually because I was running out of space and memory trying to build all using LLVM_ENABLE_PROJECTS. Also, I don't want to create a all-in-one package. Then, once

It is setting TZ and using tzset(). R is not multi-threaded so it is safe. Simon figure out the important settings from the config.log and config.h files on a musl system: /* #undef USE_INTERNAL_MKTIME */ #define HAVE_TM_GMTOFF 1 #define HAVE_TM_ZONE 1 Does this help anyone debug the issue? Simon just went on vacation. On Thu, Feb 4, 2016 at 7:32 PM, Rich Felker <dalias at libc.org>

Hi, I?m trying to compile libguestfs on Alpine Linux, that uses musl libc (lightweight, fast and simple standards-conformance libc). It fails in the check phase due to missing glibc-style extended printf formatters. -- checking for register_printf_specifier... no checking for register_printf_function... no configure: error: in `/tmp/libguestfs/src/libguestfs-1.32.6?: configure: error: No support

On 6 Jun 2017, at 21:41, Dmitry Golovin <dima at golovin.in> wrote: > > Neither is the case. The system that I want to build with this toolchain is Linux-based, but not GNUish. I would like to use musl instead of glibc and libc++ instead of libstdc++, only use binutils provided by LLVM. I think that in that case I will link libc++abi and libunwind to libc++ statically, so I will not

On 5 Jun 2017, at 15:17, Jonathan Roelofs via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 6/5/17 5:17 AM, Dmitry Golovin via llvm-dev wrote: >> I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. >> >> The configuration is the following: >> >> LIBCXX_HAS_MUSL_LIBC=ON >>

Hello, I wanted to ask if there's a reason efi/wrapper.{h,c} use __uint*_t instead of including stdint.h and using the therein defined uint*_t types? This breaks compilation of the efi blobs on systems with the musl libc since that doesn't define __uint*_t types. -- Simon Thelen

> On Dec 18, 2016, at 3:48 AM, Dmitry Golovin <dima at golovin.in> wrote: > > > > 16.12.2016, 18:23, "Vedant Kumar" <vsk at apple.com>: >>> On Dec 16, 2016, at 7:06 AM, Dmitry Golovin via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> I want to build LLVM-based toolchain with Musl, I have LLVM sources with clang and

ELLCC (http://ellcc.org), my clang/LLVM based cross development tool chain for ARM, Microblaze, Mips, Power PC, and X86, now incorporates musl (http://www.etalabs.net/musl) as its standard C library for Linux. musl is a MIT licensed, highly POSIX compliant library offering high performance and a small foot print. I spent several weeks evaluating musl before deciding to use it in ELLCC. The

>>>>> Alba Pompeo <albapompeo at gmail.com> >>>>> on Mon, 1 Feb 2016 15:33:11 -0200 writes: > Here's what I did. > svn checkout https://svn.r-project.org/R/trunk/ > cd ./trunk > aclocal -I m4 && autoconf > tools/rsync-recommended > cd .. > mkdir build > cd build > ../trunk/configure

I'm trying to build LLVM, Clang, LLD, compiler-rt, libc++, libc++abi and libunwind with musl-based toolchain. The configuration is the following: LIBCXX_HAS_MUSL_LIBC=ON LIBCXX_HAS_GCC_S_LIB=OFF CLANG_DEFAULT_CXX_STDLIB=libc++ CLANG_DEFAULT_LINKER=lld CLANG_DEFAULT_RTLIB=compiler-rt LLVM_DEFAULT_TARGET_TRIPLE=x86_64-pc-linux-musl LLVM_TARGET_ARCH=x86_64

Hi, I've updated the musl version of the clang/LLVM based ELLCC compiler suite to use musl release 0.9.14. As usual the musl guys have been doing a great job. The new release looks great! http://ellcc.org I've also started to port libunwind into ELLCC. That's the last step for a fully non-gnu run-time environment: libcxx/libcxxabi/libunwind/musl/compiler-rt for C and C++ under