Re: Updating ports that require cclang33 almost comes to a standstill!
Brooks Davis skrev 2014-07-17 16:10: On Thu, Jul 17, 2014 at 02:54:09PM +0200, Leslie Jensen wrote: Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse I suspect you need more swap. I'd recommend installing clang33 as a binary package. -- Brooks I'm still struggling with this update! I've added memory upp to 1 Gb. Swap is also 1 Gb. The error I get now does not point to shortage of memory or swap space I think. gmake[2]: Entering directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' llvm[2]: Compiling CommentHandlerTest.cpp for Release build llvm[2]: Compiling CompilationDatabaseTest.cpp for Release build llvm[2]: Compiling RecursiveASTVisitorTest.cpp for Release build c++: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. rm: /usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.d.tmp: No such file or directory gmake[2]: *** [/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' gmake[1]: *** [Tooling/.makeall] Error 2 gmake[1]: *** Waiting for unfinished jobs llvm[2]: Linking Release unit test ASTMatchers (without symbols) llvm[2]: === Finished Linking Release Unit test ASTMatchers (without symbols) gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/ASTMatchers' gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests' gmake: *** [all] Error 1 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. === make build failed for lang/clang33 /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Updating ports that require cclang33 almost comes to a standstill!
On Mon, Sep 08, 2014 at 05:48:59PM +0200, Leslie Jensen wrote: Brooks Davis skrev 2014-07-17 16:10: On Thu, Jul 17, 2014 at 02:54:09PM +0200, Leslie Jensen wrote: Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse I suspect you need more swap. I'd recommend installing clang33 as a binary package. -- Brooks I'm still struggling with this update! I've added memory upp to 1 Gb. Swap is also 1 Gb. The error I get now does not point to shortage of memory or swap space I think. gmake[2]: Entering directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' llvm[2]: Compiling CommentHandlerTest.cpp for Release build llvm[2]: Compiling CompilationDatabaseTest.cpp for Release build llvm[2]: Compiling RecursiveASTVisitorTest.cpp for Release build c++: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See URL:http://gcc.gnu.org/bugs.html for instructions. rm: /usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.d.tmp: No such file or directory gmake[2]: *** [/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' gmake[1]: *** [Tooling/.makeall] Error 2 gmake[1]: *** Waiting for unfinished jobs llvm[2]: Linking Release unit test ASTMatchers (without symbols) llvm[2]: === Finished Linking Release Unit test ASTMatchers (without symbols) gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/ASTMatchers' gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests' gmake: *** [all] Error 1 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. Please try setting MAKE_JOBS_UNSAFE=yes. Also make sure to check dmesg to see if a reason for the processing being killed. -- Brooks pgpg7bRio62TE.pgp Description: PGP signature
Re: Updating ports that require cclang33 almost comes to a standstill!
Leslie Jensen skrev 2014-07-16 11:21: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% I'm wondering if it's normal behaviour and I just have to sit it out? uname 9.1-RELEASE-p5 Thanks /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org First it stopped with this message. llvm[2]: Building Release Archive Library libclangARCMigrate.a gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/lib/ARCMigrate' gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/lib' gmake: *** [all] Error 1 === Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. === make build failed for lang/clang33 === Aborting update Then I set MAKE_JOBS_UNSAFE=yes in /etc/make.conf and got this result. ase/RecursiveASTVisitorTest.d.tmp: No such file or directory gmake[2]: *** [/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling/Release/RecursiveASTVisitorTest.o] Error 1 gmake[2]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests/Tooling' gmake[1]: *** [Tooling/.makeall] Error 2 gmake[1]: Leaving directory `/usr/ports/lang/clang33/work/llvm-3.3.src/tools/clang/unittests' gmake: *** [all] Error 1 *** [do-build] Error code 1 Stop in /usr/ports/lang/clang33. *** [build] Error code 1 Stop in /usr/ports/lang/clang33. === make build failed for lang/clang33 === Aborting update /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Updating ports that require cclang33 almost comes to a standstill!
Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Updating ports that require cclang33 almost comes to a standstill!
On Thu, Jul 17, 2014 at 02:54:09PM +0200, Leslie Jensen wrote: Dimitry Andric skrev 2014-07-17 00:10: On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry When the machine is idle these are the values. Mem: 27M Active, 236M Inact, 173M Wired, 10M Cache, 58M Buf, 21M Free Swap: 971M Total, 53M Used, 918M Free, 5% Inuse I suspect you need more swap. I'd recommend installing clang33 as a binary package. -- Brooks pgplwcKBuaavY.pgp Description: PGP signature
Updating ports that require cclang33 almost comes to a standstill!
Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% I'm wondering if it's normal behaviour and I just have to sit it out? uname 9.1-RELEASE-p5 Thanks /Leslie ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Updating ports that require cclang33 almost comes to a standstill!
On 16 Jul 2014, at 11:21, Leslie Jensen jensen.les...@gmail.com wrote: Hello list. I'm experiencing a very slow build of clang33 It seems that it's when building clang33/work/llvm-3.3 that is slows down. Using top I can see that my system is almost idle, 99,4, and cc1plus has two processes using WCPU at 1,80% and 0.10% cc1plus is actually gcc's C++ compiler, so clang isn't to blame here. :) Isn't there anything else going on, like linking (look for any 'ld' processes)? Or is the machine short on RAM (look at swap usage in top)? -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
