From: Jens Staal <staal1978@gmail.com>
To: musl@lists.openwall.com
Subject: [musl] Re: Aalbus linux : a musl/llvm libc++ based distro
Date: Fri, 8 Jan 2021 11:08:35 +0100 [thread overview]
Message-ID: <20210108100835.6ydb2b2b5y4z322y@Krypton> (raw)
In-Reply-To: <20210108100143.vvmzi3gwtuvcqy2e@Krypton>
On Fri, Jan 08, 2021 at 11:01:45AM +0100, Jens Staal wrote:
> On Thu, Jan 07, 2021 at 05:27:35AM +0100, Jens Staal wrote:
> >
> > Based on the recent announcements of compiler-rt being fixed for musl I
> > think it is relatively timely. At this moment I am using the ngtc
> > patches but hope to re-build the toolchain soon with the upstream
> > solution.
> >
>
> It has now been rebuilt with upstream so vanilla llvm seems to work now.
>
> > I am also experimenting with building musl libc with kati + samurai
> > (Ninja) as an alternative to gmake (default make in Aalbus is bmake).
> >
>
> If anyone is interested, this is the error output I get at the moment
> when I try to build musl with ckati instead of gmake:
>
> ld.lld: error: undefined hidden symbol: __dls2
> >>> referenced by dlstart.c
> >>> lto.tmp:(_dlstart_c)
> >>> did you mean: __dls3
> >>> defined in: lto.tmp
> clang-12: error: linker command failed with exit code 1 (use -v to see invocation)
> *** [lib/libc.so] Error 1
>
Oops sorry about the noise. Just when I wrote this, I saw that Gentoo
had hit the same bug with musl when -flto is set in CFLAGS. Removing
that actually makes it work!
So ckati CAN be used as an alternative to gmake for musl.
>
> so something ckati does with the ld.lld linker in the generation of the
> build.ninja file is not working for musl. The linker is working and ckati is
> working on other projects (including itself)
>
>
> >
prev parent reply other threads:[~2021-01-08 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 4:27 [musl] " Jens Staal
2021-01-08 10:01 ` [musl] " Jens Staal
2021-01-08 10:08 ` Jens Staal [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=20210108100835.6ydb2b2b5y4z322y@Krypton \
--to=staal1978@gmail.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).