mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rob Landley <rob@landley.net>
To: musl@lists.openwall.com
Cc: sabotage@lists.openwall.com
Subject: Re: [ANN] sabotage mips(el) 0.9.7+ rootfs tarballs are available
Date: Sat, 01 Dec 2012 01:01:28 -0600	[thread overview]
Message-ID: <1354345288.2190.31@driftwood> (raw)
In-Reply-To: <50B96E0F.3030902@barfooze.de> (from maillist-musl@barfooze.de on Fri Nov 30 20:40:15 2012)

On 11/30/2012 08:40:15 PM, John Spencer wrote:
> 
> this is based on musl 0.9.7, with all mips patches applied.
> so it really is more or less 0.9.8 minus the ppc port.
> 
> it takes about 2-3 weeks to get everything built in qemu mips,
> so i didnt restart the build when 0.9.8 came out.

Wow, really?

Beyond distcc, I looked at cluster based approaches but they all  
leverage distro repositories. Basically you have a "master" node that  
hands out work to "slave" nodes which start out all using the same  
filesystem, the master works otu which packages it can build with out  
dependencies and hands them out to the "slave" nodes, which build them,  
create a binary package (.rpm, .deb, the portage binary thing, etc) and  
sends it back to the "master" node which loads them into the  
repository. The master then hands out more work to the idle slave nodes  
using only packages which have prerequisites that can be installed from  
the repository rather than built.

(I looked into having them all share a network root filesystem and  
having the master node update it, but running ./configure while a  
package shows up out from under you is kinky.)

I also covered setting up tun/tap for kvm/qemu here:

   http://landley.net/lxc/02-networking.html

(That covers more than you'd need, but if you have a 4-way machine you  
can get a small cluster setup that way, and each qemu instance gets a  
cpu to itself...)

Rob

      reply	other threads:[~2012-12-01  7:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-01  2:40 John Spencer
2012-12-01  7:01 ` Rob Landley [this message]

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=1354345288.2190.31@driftwood \
    --to=rob@landley.net \
    --cc=musl@lists.openwall.com \
    --cc=sabotage@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).