From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: musl + libc++
Date: Tue, 22 Mar 2016 13:28:48 +0100 [thread overview]
Message-ID: <20160322122848.GF9862@port70.net> (raw)
In-Reply-To: <2C455331-61AF-4818-BB41-B95F911B3F48@gmail.com>
* Lei Zhang <zhanglei.april@gmail.com> [2016-03-22 20:05:29 +0800]:
> On Mar 22, 2016, at 7:48 PM, Luca Barbato <lu_zero@gentoo.org> wrote:
> >
> > On 22/03/16 04:43, Lei Zhang wrote:
> >> 2016-03-22 7:39 GMT+08:00 Hayden Livingston <halivingston@gmail.com>:
> >>
> >>> Have folks gotten around using musl + libc++ (from the llvm project)?
> >>>
> >>> I'm trying to get a setup where all my dependencies can be moved to
> >>> musl and libc++ to build static executables.
> >>>
> >>
> >> I've tried to do about the same thing before and failed because libc++
> >> depends on some functions not implemented in musl yet, like strtoll_l()
> >> and __printf_chk() IIRC.
> >
> > Nothing should directly use __printf_chk() how did you get that symbol
> > there?.
>
> Well, I manually linked a toy C++ program with musl and libc++, and when I ran the program the dynamic linker complained about not finding a bunch of symbols, including strtoll_l, __printf_chk, etc. Perhaps I mistakenly messed musl with glibc somehow...
>
you probably used a libc++ built against glibc.
that should work on x86_64 if you provide the missing
symbols (e.g. LD_PRELOAD a dso with a dummy strtoll_l
and __printf_chk).
but it is better to build the entire toolchain for
musl instead of doing musl-gcc like wrapping for
c++ even if you can get the wrapper to work.
e.g. a libstdc++ built against glibc works for simple
things but can be broken for multi-threaded code.
next prev parent reply other threads:[~2016-03-22 12:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 23:39 Hayden Livingston
2016-03-22 3:43 ` Lei Zhang
2016-03-22 11:48 ` Luca Barbato
2016-03-22 12:05 ` Lei Zhang
2016-03-22 12:28 ` Szabolcs Nagy [this message]
2016-03-22 11:10 ` Christian Neukirchen
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=20160322122848.GF9862@port70.net \
--to=nsz@port70.net \
--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).