From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: C++ questions
Date: Tue, 9 Jun 2015 16:25:50 -0400 [thread overview]
Message-ID: <20150609202550.GP17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAGDMk9Ebt-LiFW_AiP0H3_w=ZJuTkptFzZm6caJg8bNzCL3f=g@mail.gmail.com>
On Tue, Jun 09, 2015 at 04:17:11PM -0400, John Mudd wrote:
> On Fri, Jun 5, 2015 at 5:56 PM, Szabolcs Nagy <nsz@port70.net> wrote:
>
> > * John Mudd <johnbmudd@gmail.com> [2015-06-05 17:34:52 -0400]:
> > > Error loading shared library ld-linux.so.2: No such file or directory
> > > (needed by /usr/lib/i386-linux-gnu/libstdc++.so.6)
> > >
> >
> > create an empty ld-linux.so.2
> >
> > gcc -o ld-linux.so.2 -xc -shared - </dev/null
> >
> > (nowadays toolchains sometimes add the dynamic linker to
> > elf DT_NEEDED, i dont know why, it's not really needed)
> >
> > > I looked at the notes about C++ in the musl faqs. For that I decided it
> > > might help if I built gcc in musl. Then everything will be musl-ized? I
> > > built gmp, mpfr and mpc. Started building gcc but got the following
> > error.
> > >
> > > /home/mudd/musl/gcc-4.9.2.obj/gcc/../../gcc-4.9.2/gcc/plugin.c:579:
> > > undefined reference to `dlopen'
> > >
> >
> > you have to patch gcc and use certain options to make it work
> >
> > musl-cross build scripts take care of if
> > (there are prebuilt toolchains too)
> >
> > > Before I go further, any opinions if I'm even headed in the right
> > direction?
> >
> > you may get away without building
>
> Thanks again. Adding the empty ld-linux.so.2 helped. I also had to
> add libgcc_s.so.1 and the following _chk stubs.
>
> http://pastebin.com/TeieBKCE
New ABI compat coming up soon (hopefully in the next release) will
eliminate the need to add these yourself -- and the ones we add will
actually perform the correct overflow/etc. checks.
Rich
prev parent reply other threads:[~2015-06-09 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-05 21:34 John Mudd
2015-06-05 21:56 ` Szabolcs Nagy
2015-06-05 22:57 ` John Mudd
2015-06-09 20:17 ` John Mudd
2015-06-09 20:25 ` Rich Felker [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=20150609202550.GP17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).