mailing list of musl libc
 help / color / mirror / code / Atom feed
From: agent <agentprog@gmail.com>
To: musl@lists.openwall.com
Subject: Re: STLport
Date: Mon, 31 Dec 2012 12:33:00 +0600	[thread overview]
Message-ID: <50E1319C.1060301@gmail.com> (raw)
In-Reply-To: <1716568.15394.1356922853329.JavaMail.root@grantgray.id.au>

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

31.12.2012 09:00, Grant Gray пишет:
>
>     On Mon, Dec 31, 2012 at 12:11:18PM +1100, Grant Gray wrote:
>     > Hi list,
>     >
>     >
>     > Is anyone working on getting STLport working with musl?
>     >
>     >
>     > I had a quick look at the STLport sources and it seems to assume
>     > glibc is in use if the toolchain is GCC, so it seems some porting
>     > effort is required to get it working with musl.
>
>     Is there a reason you want to use STLport rather than libstdc++ or
>     libc++? My impression was that STLport was outdated, unmaintained, and
>     full of ugly legacy hackery from the 90s...
>
>     Rich
>
> Licensing is the issue. I'm building a userland free of copyleft code, 
> which rules out libstdc++. I haven't investigated libc++, but I have 
> no allegiance to STLport so will look into it.
>
> Is anyone already working on a libc++ integration with musl?
>
i have tried to build the whole stack: clang, libc++, libc++abi with 
musl, though i got stuck with libunwind for libc++abi. libc++ compiled 
fine when using libsupc++, but i didn't test it anyhow (maybe it is even 
unusable). i'm going to try out clang + libc++ + libcxxrt + musl 
soon.they say libc++ works with libcxxrt and libcxxrt has it's own unwind.

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

  parent reply	other threads:[~2012-12-31  6:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <16264585.15369.1356916055281.JavaMail.root@grantgray.id.au>
2012-12-31  1:11 ` STLport Grant Gray
2012-12-31  1:43   ` STLport Luca Barbato
2012-12-31  2:06   ` STLport Rich Felker
2012-12-31  2:58     ` STLport idunham
2012-12-31  3:00     ` STLport Grant Gray
2012-12-31  3:07       ` STLport Rich Felker
2012-12-31  6:33       ` agent [this message]
2012-12-31  7:57         ` STLport Daniel Cegiełka
2012-12-31 17:37           ` STLport Rich Felker
2012-12-31 15:29         ` STLport 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=50E1319C.1060301@gmail.com \
    --to=agentprog@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).