mailing list of musl libc
 help / color / mirror / code / Atom feed
From: John Mudd <johnbmudd@gmail.com>
To: musl <musl@lists.openwall.com>
Cc: John Mudd <johnbmudd@gmail.com>
Subject: Re: C++ questions
Date: Fri, 5 Jun 2015 18:57:01 -0400	[thread overview]
Message-ID: <CAGDMk9E=ooET-De-G4tL4PXxf-yk82NzEUbUZM_Rn_RwnMrHbw@mail.gmail.com> (raw)
In-Reply-To: <20150605215616.GF10927@port70.net>

[-- Attachment #1: Type: text/plain, Size: 1189 bytes --]

Thanks. I recognize the "create empty lib" advice. Will try asap but
heading to airport now.
On Jun 5, 2015 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
>

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

  reply	other threads:[~2015-06-05 22:57 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 [this message]
2015-06-09 20:17   ` John Mudd
2015-06-09 20:25     ` Rich Felker

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='CAGDMk9E=ooET-De-G4tL4PXxf-yk82NzEUbUZM_Rn_RwnMrHbw@mail.gmail.com' \
    --to=johnbmudd@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).