From: Gregor Richards <gr@purdue.edu>
To: musl@lists.openwall.com
Cc: Isaac Dunham <idunham@lavabit.com>
Subject: Re: Draft: musl promo materials
Date: Sat, 14 Jul 2012 19:30:38 -0400 [thread overview]
Message-ID: <5002011E.6070503@purdue.edu> (raw)
In-Reply-To: <20120714160641.25a2e7be@newbook>
On 07/14/2012 07:06 PM, Isaac Dunham wrote:
> On Sat, 14 Jul 2012 14:45:40 -0700
> Charlie Kester <corky1951@comcast.net> wrote:
>
>
>> It would be good to include a list of apps that have been
>> successfully compiled with musl. No need to list every such app,
>> just some representative ones that will help dispel any fears about
>> the library's ability to replace glibc in the most common uses.
> Somehow, listing compatible applications in PR does not
> sound very encouraging, until you can run the really huge
> suites/applications (I'm thinking of glibc-linked NVIDIA + Xorg, as was
> recently done with a patched version of musl, Google Earth, or
> native-built OpenOffice, Firefox/Chromium, the GIMP, Wine, Java, Mesa,
> GNOME, KDE, maybe Xfce, R, GRASS, BRL-CAD, FreeCAD, TeX, GDAL...the
> list isn't exclusive or a recommendation of the software, but it
> should give an idea of the scale I'm talking about). If you say "can
> run GCC 4.7, PHP, Xfbdev, Xfce 4.10, SDL, Tomoyo and grsec" (Xfce is in
> Snowflake, the rest are the big names from sabotage), that sure seems
> to reinforce the impression you're concerned about by virtue of
> omission.
> I'd prefer to see a link to "further information and compatability" or
> some such thing.
>
> Isaac Dunham
>
GIMP and XFCE work. I'm working on Firefox, but I believe it currently
hits a bug in musl's dlopen, so I'm waiting on that fix. It compiles, it
just doesn't launch (hyuk). I routinely run the complete pkgsrc suite
through musl to see what works; the current test is ongoing, but here's
the results of the most recent one, which unfortunately suffered from
some bugs in my setup and so has some false build failures:
Tried 10444, depfail 4489, depok 5955, nobuild 2454, testfail 336,
success 3165 (53.1486%). Breakdown: http://sprunge.us/jgDO . MVD:
http://sprunge.us/cjRK
(Tried = packages attempted, depfail = deps failed to build, nobuild =
didn't build, testfail = built but tests failed, success = all tests
passed, percentage is out of depok, MVD = most valuable dependencies, of
which I have since fixed security/p5-Crypt-Rijndael and textproc/xmlrpc-c )
I suppose I'll post the results of the latest run on the mailing list
once it's done. I've mainly stuck to the IRC channel.
With valediction,
- Gregor Richards
next prev parent reply other threads:[~2012-07-14 23:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:12 Rich Felker
2012-07-13 19:16 ` Szabolcs Nagy
2012-07-14 6:40 ` orc
2012-07-13 23:30 ` Rich Felker
2012-07-14 19:05 ` Isaac Dunham
2012-07-15 0:01 ` Rich Felker
2012-07-14 21:45 ` Charlie Kester
2012-07-14 23:06 ` Isaac Dunham
2012-07-14 23:30 ` Gregor Richards [this message]
2012-07-15 0:49 ` Isaac Dunham
2012-07-15 0:58 ` Gregor Richards
2012-07-15 0:03 ` 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=5002011E.6070503@purdue.edu \
--to=gr@purdue.edu \
--cc=idunham@lavabit.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).