From: Gregor Richards <gr@purdue.edu>
To: Isaac Dunham <idunham@lavabit.com>
Cc: musl@lists.openwall.com
Subject: Re: Latest pkgsrc results [What builds on musl 0.9.7?]
Date: Wed, 21 Nov 2012 21:36:47 -0800 [thread overview]
Message-ID: <50ADB9EF.1050407@purdue.edu> (raw)
In-Reply-To: <20121121181308.0b69d5b4.idunham@lavabit.com>
I recall looking into the Sabotage patches for Apache before, but
concluding that the way pkgsrc builds Apache makes it sort of a pain. I
may look into it again, but frankly it's pretty low on my priority list.
The patches exist out there (in Sabotage), so it's not like musl users
can't get Apache to build.
Qt4 is actually near working, if I devoted some time I'm confident I
could get it building. gnutls I haven't looked at, but I'd appreciate if
somebody did.
gimp indeed doesn't build. I'll take a look.
libdrm fails due to an out of date patch for libpciaccess. I'll just
have to fix that ^^´
With valediction,
- Gregor Richards
On 11/21/2012 06:13 PM, Isaac Dunham wrote:
> On Tue, 20 Nov 2012 21:47:05 -0800
> Gregor Richards <gr@purdue.edu> wrote:
>
>> Here are the results from my latest build of NetBSD pkgsrc 2012Q3 on
>> musl 0.9.7, with patches from
>> http://bitbucket.org/GregorR/musl-pkgsrc-patches revision 98b82c29f04c.
>>
>> Attempted: 10704
>> Deps failed: 3118
>> Build tried: 7586
>> Build failed: 1155
>> Tests failed: 346
>> Success: 6085 (80.2136%)
> Looking good...
>
>> Breakdown:
>> https://sites.google.com/a/codu.org/musl/pkgsrc-results/pkgsrc-results-2012Q3-98b82c29f04c-musl-0.9.7-breakdown.txt?attredirects=0&d=1
>> or http://wiki.musl-libc.org/pkgsrc_results
>> Archive:
>> https://sites.google.com/a/codu.org/musl/pkgsrc-results/pkgsrc-results-2012Q3-98b82c29f04c-musl-0.9.7.tar.gz?attredirects=0&d=1
>>
>>
>> Notes:
>>
>> In the breakdown, 'D' means dependencies, 'B' means build, 'T' means
>> tests. Blank is success, 'X' is failure.
> OK, I see that apache doesn't build...sabotage has patches for that.
> OpenMotif and mpg123 should be easy fixes (they built without patching a while back); I expect it's just CFLAGS.
> gnutls, Qt 3 & 4, m17n-db, and libcanberra are the most valuable dependencies.
> Heirloom-libcommon looks pretty important, but that's thanks to how pkgsrc treats the heirloom toolchest.
>
> libusb should use the same patch as libusbx; I actually followed something on "How to build libusb for android" when I did that.
>
> It's claiming that the Gimp doesn't build-is that correct?
>
> I wonder what's blocking libdrm...
>
>> If you have patches to make other packages build, please report them on
>> the musl-pkgsrc-patches issue tracker:
>> https://bitbucket.org/GregorR/musl-pkgsrc-patches/issues .
>> As with all of my repositories, musl-pkgsrc-patches is also available
>> via git: http://github.com/GregorR/musl-pkgsrc-patches .
>>
>> If you reply to this email, please reply-all. (I am not presently
>> subscribed to this mailing list, as it has no digest option.)
>>
>> With valediction,
>> - Gregor Richards
next prev parent reply other threads:[~2012-11-22 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 5:47 Gregor Richards
2012-11-22 2:13 ` Isaac Dunham
2012-11-22 2:22 ` Rich Felker
2012-11-22 5:36 ` Gregor Richards [this message]
2012-11-22 7:34 ` Isaac Dunham
2012-11-22 7:37 ` Gregor Richards
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=50ADB9EF.1050407@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).