mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rashad Kanavath <mohammedrashadkm@gmail.com>
To: musl@lists.openwall.com
Subject: Re: using musl with a c++ library.
Date: Tue, 29 Mar 2016 13:41:31 +0200	[thread overview]
Message-ID: <CANNqv9fhkne2ReveHBXR3NeY52AkeMFVUL6wcTd=FuffOeG8Cg@mail.gmail.com> (raw)
In-Reply-To: <95A8D906-77D6-429E-93F5-E859974D593B@shiz.me>

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

Hello Shiz,

Thanks for your reply. I will try links you said and let you know how it
goes..

On Tue, Mar 29, 2016 at 12:26 PM, Shiz <hi@shiz.me> wrote:

>
> > On 29 Mar 2016, at 11:02, Rashad Kanavath <mohammedrashadkm@gmail.com>
> wrote:
> >
> > should I rebuild just libstdc++ using musl-gcc wrapper script and use
> that libstdc++ ?.
>
> I believe the current recommendation is to not use musl-gcc at all for C++
> stuff,
> but just build a proper musl-native toolchain. Recipes for such can be
> found at [1] and [2].
> musl-gcc is just a wrapper for convenience, but definitely not a
> replacement for a proper
> native toolchain.
>
> > Also Is it possible to distribute musl with an application package.
> Currently I have a self-extracting archive which uses an older version of
> glibc. so it will run on any platform that has a glibc version higher that
> it was build (2.4). If I use musl and is able to distribute it along with
> my application package, Then I don't have to rely on anything other than
> linux kernel version on the target platform.
>
> Yes, as musl is licensed under the MIT license, this is allowed.
> You could even statically link against it to be able to ship just a single
> binary file.
>
> - Shiz
>
> [1]: https://bitbucket.org/GregorR/musl-cross
> [2]: https://github.com/richfelker/musl-cross-make
>



-- 
Regards,
   Rashad

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

      reply	other threads:[~2016-03-29 11:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29  9:02 Rashad Kanavath
2016-03-29 10:26 ` Shiz
2016-03-29 11:41   ` Rashad Kanavath [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='CANNqv9fhkne2ReveHBXR3NeY52AkeMFVUL6wcTd=FuffOeG8Cg@mail.gmail.com' \
    --to=mohammedrashadkm@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).