From: Dave Butler <daveb@tanagerproductions.com>
To: musl@lists.openwall.com
Subject: Re: Updated documentation on cross building LLVM for Musl
Date: Wed, 13 Feb 2019 13:18:40 -0600 [thread overview]
Message-ID: <CANm61jdTpL6t0XFe4Xf8tq6Sa++HiOTOsHGiodo9Xq3R_CRaXQ@mail.gmail.com> (raw)
In-Reply-To: <45c155b8-52cb-5d6b-2daa-12c4f22a55c2@adelielinux.org>
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
On Wed, Feb 13, 2019 at 1:13 PM A. Wilcox <awilfox@adelielinux.org> wrote:
> On 02/13/19 12:59, Croepha wrote:
> >
> > I spent some time figuring out how to get Clang and related tools to
> > build against musl starting from a Glib system. The result is a
> > GNU-less (no libgcc, libstdc++, and GNU LD, AR...) toolchain. I figured
> > I'd share in the hopes that someone else may find it useful...
> >
> > Note: Clang and friends works as expected, but I couldn't get the
> > sanitizers to build against Musl, so that is the only limitation that I
> > am aware of...
> >
> > Full doc here:
> > https://gist.github.com/croepha/cdaf30638109b1a949f35aa215a7c86d
> >
> > --Dave
> >
> >
>
> Beginning of document:
>
> # LLVM seems to work great on Musl, there only seems some build errors
> # when trying to build the sanitizers. So sanitizers have been enabled.
>
> You probably mean "disabled".
>
> Yes!, thanks for pointing that out, fixed now
> Thanks for this. Does LLVM have things like ar(1), as(1), nm(1) and
> friends as well? So you really don't need binutils?
>
> Yes, LLVM's versions of those files are llvm-ar, llvm-as, and llvm-nm, but
you can just make simlinks to as, as and nm
I was able to build a few things with that toolchain without GNU binutils,
haven't found any deal-breaking limitations so far...
> Best,
> --arw
>
> --
> A. Wilcox (awilfox)
> Project Lead, Adélie Linux
> https://www.adelielinux.org
>
>
[-- Attachment #2: Type: text/html, Size: 2499 bytes --]
prev parent reply other threads:[~2019-02-13 19:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 18:59 Croepha
2019-02-13 19:13 ` A. Wilcox
2019-02-13 19:18 ` Dave Butler [this message]
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=CANm61jdTpL6t0XFe4Xf8tq6Sa++HiOTOsHGiodo9Xq3R_CRaXQ@mail.gmail.com \
--to=daveb@tanagerproductions.com \
--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).