Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 31 Dec 2012 12:33:00 +0600
From: agent <>
Subject: Re: STLport

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.

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.