From: Dmitry Golovin <dima@golovin.in>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: Re: clang/musl/linux?
Date: Tue, 07 Aug 2018 16:38:03 +0300 [thread overview]
Message-ID: <1011541533649083@iva4-406defa25fee.qloud-c.yandex.net> (raw)
In-Reply-To: <CAOUYtQBAM9dWnz0uGmCz-RR27UanM8M9CEYwRiUwGYgBFJDm5Q@mail.gmail.com>
07.08.2018, 16:19, "Jon Chesterfield" <jonathanchesterfield@gmail.com>:
> I'm interested in using a toolchain containing clang, musl and the llvm C++ stack from a glibc linux host. There is some patchy documentation on doing this which suggests it is possible with some relatively minor patches. Most of the links are from a few years ago.
>
> Does anyone on this list use a similar setup today? If so, does it work for you?
>
> Essentially I'm hoping for guidance on whether the end result of the cmake hackery would be stable enough to use as my daily toolchain, before grinding through the inevitable plumbing.
>
> Thanks!
>
> Jon
Unfortunately, it's not possible to build mainline linux with clang right now. Currently most efforts on patching the kernel are combined in this repo: https://github.com/ClangBuiltLinux/linux (it is also not ready to be compiled yet).
You can also check my GNU-free toolchain as a starting point: https://github.com/tpimh/ngtc
It uses musl, clang, lld and libcxx with very little patching.
Regards,
Dmitry
next prev parent reply other threads:[~2018-08-07 13:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 13:19 clang/musl/linux? Jon Chesterfield
2018-08-07 13:38 ` Dmitry Golovin [this message]
2018-08-31 6:29 ` clang/musl/linux? Fāng-ruì Sòng
2018-08-31 7:19 ` clang/musl/linux? Dmitry Golovin
2018-08-31 8:29 ` clang/musl/linux? Luca Barbato
2018-08-31 11:30 ` clang/musl/linux? Jon Chesterfield
2018-08-31 11:50 ` clang/musl/linux? Dmitry Golovin
2018-08-31 13:13 ` clang/musl/linux? Jon Chesterfield
2018-08-31 14:24 ` clang/musl/linux? Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1011541533649083@iva4-406defa25fee.qloud-c.yandex.net \
--to=dima@golovin.in \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).