>From libgcc-devel, I suspect. https://trac.macports.org/ticket/40284
I am experiencing this problem on Mountain Lion. Were the Lion and Mountain Lion buildbots not affected? On Sep 4, 2013, at 18:40, William Siegrist <[email protected]> wrote: > There was a rogue cc1 process causing a bunch of memory to swap so I rebooted > the slave. > > -Bill > > > On Sep 4, 2013, at 3:23 PM, Christoph Iserlohn <[email protected]> wrote: > >> see for example: >> https://build.macports.org/builders/buildports-snowleopard-x86_64/builds/20399/steps/compile/logs/stdio >> >> | tee: /var/tmp/portresults/nodejs.log: No space left on device >> | x ./opt/local/bin/macho-dump-mp-3.3: Seek failed: Invalid argument >> | x ./opt/local/bin/opt-mp-3.3: Seek failed: Invalid argument >> | tee: /var/tmp/portresults/nodejs.log: No space left on device >> | tar: Error exit delayed from previous errors. >> | tee: /var/tmp/portresults/nodejs.log: No space left on device >> | Command failed: /usr/bin/bzip2 -d -c >> /opt/local/var/macports/software/llvm-3.3/llvm-3.3-3.3_1.darwin_10.x86_64.tbz2 >> | ( /usr/bin/tar -xvpf - ) >> | tee: /var/tmp/portresults/nodejs.log: No space left on device _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
