From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] Build process optimisation
Date: Wed, 6 Apr 2016 14:03:02 +0200 [thread overview]
Message-ID: <2030a7c1db616b194e2fb896f8f1e135@felloff.net> (raw)
In-Reply-To: <57045E89.7000202@qs.co.nz>
waiiit... 30 minutes churning over libraries? this is way too slow,
your vbox is crap, dont use it.
doing mk libs, which does mk clean in each lib before rebuilding gives me
30 *seconds* over remote fileserver... locally its more like 14 seconds
on my pentium d fileserver.
cd /sys/src; time mk libs
...
11.00u 10.39s 28.94r mk libs
and just mk (without mk clean in each lib) gives me 10 seconds:
time rc -c 'for(i in lib*){cd $i && mk && cd ..}'
...
1.07u 2.17s 10.29r rc -c for(i in lib*){cd $i && mk && cd ..}
if you just do "mk" in /sys/src, it does not clean the libraries.
if you do not want to touch the libraries, just do mk in /sys/src/cmd
or some other individual sub-directory if you know the dependencies
are fine already.
--
cinap
next prev parent reply other threads:[~2016-04-06 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 0:55 Trevor Higgins
2016-04-06 1:05 ` [9front] " Nicolas Owens
2016-04-06 12:03 ` cinap_lenrek [this message]
2016-04-06 23:26 ` Plan9
2016-04-06 23:35 ` sl
2016-04-06 23:37 ` cinap_lenrek
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=2030a7c1db616b194e2fb896f8f1e135@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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.
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).