From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com,
Michele Portolan <michele.portolan@grenoble-inp.fr>
Subject: Re: New to musl and C++ compiling
Date: Mon, 21 Jan 2019 13:02:24 +0100 [thread overview]
Message-ID: <20190121120224.GS21289@port70.net> (raw)
In-Reply-To: <20190121115313.GR21289@port70.net>
* Szabolcs Nagy <nsz@port70.net> [2019-01-21 12:53:13 +0100]:
> * Michele Portolan <michele.portolan@grenoble-inp.fr> [2019-01-21 11:24:12 +0100]:
> > Hello,
> >
> > I just installed MUSL because I have a C++ multithreaded application that
> > uses threads heavily and I would like to make it independent from an OS. I
> > was able to easily install and run MUSL for C targets, but when I try a
> > simple C++ Hello world I get an error for the standard libs.
> >
> > My file is the simplest possible (no multithreading to start with):
> >
> > #include <iostream>
> >
> > int main() {
> > std::cout << "Hello, World" << std::endl;
> > return 0;
> > }
> >
> > Here is my output for standard and musl-based compilation.
> >
> > portolan@noumea:~/musl/examples$ g++ -o test_cpp test_cpp.cpp
> > portolan@noumea:~/musl/examples$ ./test_cpp
> > Hello, World
> > portolan@noumea:~/musl/examples$ g++ -o test_cpp test_cpp.cpp -specs
> > "/home/portolan/musl/install/lib/musl-gcc.specs"
>
> for c++ the recommended practice is to use a cross compiler that
> is built for musl, instead of a glibc based native compiler with
> a specs file or other wrapping mechanism, because c++ headers are
> difficult to get right: in this case the specs file disabled all
> c++ header paths, you need to add those back manually, see
>
> g++ -v -E -xc++ - </dev/null
>
> but there may be still issues
> - the header ordering matters as libstdc++ uses include_next and
> - some headers are installed based on the libc found at configure
> time of gcc, so the abi is slightly different depending on what
> libc you built your compiler for,
> - e.g. with static linking (which you need if you want a portable
> executable) one issue is that libstdc++ has a broken way to
> detect multi-threadedness and all locks become nops (unless your
> binary has a definition for the 'pthread_cancel' symbol).
> if gcc is configured for *-musl* this is fixed.
>
> in short: use a cross compiler targetting *-linux-musl, there are
> prebuilt ones at http://musl.cc/
> (note that you will have to build and install all your application
> dependencies into a path where the cross compiler can find them)
oh and if you have many dependencies then the simplest way is of
course to use a musl based distro (alpine, void, adelie,..) then
you can use all the prebuilt packages and the native toolchain
with g++ -static and you get a portable executable.
(setting up a chroot or docker with whatever distro should not be
too much work).
> > test_cpp.cpp:1:11: fatal error: iostream: No such file or directory
> > #include <iostream>
> > ^~~~~~~~~~
> > compilation terminated.
> >
> > I am probably missing something REALLY basic, at least I hope so!
> >
> > Best regards,
> >
> >
> > Michele
next prev parent reply other threads:[~2019-01-21 12:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-21 10:24 Michele Portolan
2019-01-21 11:53 ` Szabolcs Nagy
2019-01-21 12:02 ` Szabolcs Nagy [this message]
2019-01-21 13:13 ` Michele Portolan
2019-01-21 13:55 ` Szabolcs Nagy
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=20190121120224.GS21289@port70.net \
--to=nsz@port70.net \
--cc=michele.portolan@grenoble-inp.fr \
--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).