List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
On Fri, Mar 4, 2011 at 6:46 PM, Alex Alexander <firstname.lastname@example.org> wrote:
> Anyway, compilation on a modern system shouldn't take more than an
> hour. ~15-20 minutes on a quad i5.
Clearly your definition of modern doesn't include my server... :)
Just checked and the last build clocked in at 192 minutes. I need to
make sure I have /var/tmp/portage symlinked back to a non-tmpfs
location whenever I build it or else the system pretty-much dies from
a lack of RAM.
For kicks I tried to do better with distcc and EC2. That worked great
until it started running a bunch of python scripts in the makefile -
at -j15 or whatever I had it set to. Distcc really needs a solution
for the fact that you can't pick a single optimum value for -j when
gcc is only part of the build. Sure, the EC2 latency isn't great, but
you can parallelize as much as you want, and for me the bigger benefit
is not sucking down half a gig of RAM.
Still, the build has gotten faster with time as the excellent g.o
chromium team slowly strips out bundled libs. If you want a real
eye-opener do a du -s * in the source tree for chromium and see where
all the code is.