mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Gregor Richards <gr@purdue.edu>
To: musl@lists.openwall.com
Subject: Latest pkgsrc results [What builds on musl 0.9.12?]
Date: Tue, 17 Sep 2013 11:29:57 -0400	[thread overview]
Message-ID: <52387575.4000207@purdue.edu> (raw)

Here are the results from my latest build of NetBSD pkgsrc 2013Q2 on 
musl 0.9.12, with patches from 
http://bitbucket.org/GregorR/musl-pkgsrc-patches revision 999f342e0633.

Attempted:	11274
Deps failed:	3336
Build tried:	7938
Build failed:	919
Tests failed:	1811
Success:	5208 (65.6085%)

Breakdown:
http://musl.codu.org/pkgsrc-results/pkgsrc-results-2013Q2-999f342e0633-musl-0.9.12-breakdown.txt?attredirects=0&d=1 
or http://wiki.musl-libc.org/pkgsrc_results (once the wiki is working 
and I can update it)
Archive:
http://musl.codu.org/pkgsrc-results/pkgsrc-results-2013Q2-999f342e0633-musl-0.9.12.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.

Yes, I know musl 0.9.13 is already out. It took me a while to run these, OK!

Perl had strange problems this time 'round. Didn't seem to be related to 
musl though. This particularly influenced tests for all Perl packages, 
bringing down the overall success rate artificially.

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



                 reply	other threads:[~2013-09-17 15:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=52387575.4000207@purdue.edu \
    --to=gr@purdue.edu \
    --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).