From: Mike Viau on 25 Jul 2010 00:00 > On Sat, 24 Jul 2010 22:22:29 -0500 <stan(a)hardwarefreak.com> wrote: > > Setting CONCURRENCY_LEVEL=4 in your user environment should fix this, at > least, it used to. From the bash command line, for the current session only: > > export CONCURRENCY_LEVEL=4 > > To make it permanent you need to edit /home/[user]/.bash_profile and append: > > export CONCURRENCY_LEVEL=4 > > If you regularly do your kernel work while logged on as root, you'd need to > append it to /root/.bashrc or /root/.profile You might also want to read http://www.wowway.com/~zlinuxman/Kernel.htm or from google's cache at http://webcache.googleusercontent.com/search?q=cache:7D7TfZqA1wMJ:www.wowway.com/~zlinuxman/Kernel.htm+http://www.wowway.com/~zlinuxman/Kernel.htm&cd=4&hl=en&ct=clnk&gl=ca -M _________________________________________________________________ Game on: Challenge friends to great games on Messenger http://go.microsoft.com/?linkid=9734387
From: Celejar on 25 Jul 2010 00:20 On Sat, 24 Jul 2010 22:22:29 -0500 Stan Hoeppner <stan(a)hardwarefreak.com> wrote: > Curt Howland put forth on 7/24/2010 8:49 PM: > > > Not compiling often (as you can tell), I note that the compile is > > using only one cpu of 4 at a time. I'm sure there is a parallel > > compilation tweak somewhere. > > Setting CONCURRENCY_LEVEL=4 in your user environment should fix this, at > least, it used to. From the bash command line, for the current session only: > > export CONCURRENCY_LEVEL=4 > > To make it permanent you need to edit /home/[user]/.bash_profile and append: > > export CONCURRENCY_LEVEL=4 > > If you regularly do your kernel work while logged on as root, you'd need to > append it to /root/.bashrc or /root/.profile And assuming you're using kernel-package, from its manpage: --jobs number -j number Set the environment variable CONCURRENCY_LEVEL to "number". Celejar -- foffl.sourceforge.net - Feeds OFFLine, an offline RSS/Atom aggregator mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/20100725001136.f19fdb7f.celejar(a)gmail.com
From: Sven Joachim on 25 Jul 2010 03:30 On 2010-07-25 03:49 +0200, Curt Howland wrote: > Not compiling often (as you can tell), I note that the compile is > using only one cpu of 4 at a time. I'm sure there is a parallel > compilation tweak somewhere. Yes, the "-j" switch for make. If you want to build a Debian package that you can install and test, use "make -j4 deb-pkg". Sven -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/87eiesnhvt.fsf(a)turtle.gmx.de
From: Sven Joachim on 25 Jul 2010 03:30 On 2010-07-25 05:22 +0200, Stan Hoeppner wrote: > Curt Howland put forth on 7/24/2010 8:49 PM: > >> Not compiling often (as you can tell), I note that the compile is >> using only one cpu of 4 at a time. I'm sure there is a parallel >> compilation tweak somewhere. > > Setting CONCURRENCY_LEVEL=4 in your user environment should fix this, at > least, it used to. This only works if you use kernel-package to build the kernel. The generic way is to use "make -j4". > If you regularly do your kernel work while logged on as root, you'd need to > append it to /root/.bashrc or /root/.profile There is no need to ever build the kernel as root. Sven -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/87k4okni2i.fsf(a)turtle.gmx.de
From: Curt Howland on 25 Jul 2010 12:50 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sunday 25 July 2010, Sven Joachim <svenjoac(a)gmx.de> was heard to say: > > Setting CONCURRENCY_LEVEL=4 in your user environment should fix > > this, at least, it used to. > > This only works if you use kernel-package to build the kernel. The > generic way is to use "make -j4". Excellent advice to the novice. > There is no need to ever build the kernel as root. Strangely enough, I wasn't. Not quite _that_ novice I guess. :^) Now on to something new: Build failure! Who'd'a thought? I changed back to single-concurrency just to make sure that it wasn't related, "make clean", then tried again with the same result. Any suggestions? ========== $ make-kpkg --revision=curt0.1 kernel_image {scrolled so many as I'm sure you know... Then,} make[1]: Leaving directory `/usr/src/linux-2.6.35-rc6' /usr/bin/make -j1 ARCH=i386 \ -C Documentation/lguest make[1]: Entering directory `/usr/src/linux-2.6.35-rc6/Documentation/lguest' cc -m32 -Wall -Wmissing-declarations -Wmissing-prototypes -O3 -I../../include -I../../arch/x86/include -U_FORTIFY_SOURCE lguest.c -o lguest lguest.c:21:25: error: sys/eventfd.h: No such file or directory lguest.c: In function 'create_thread': lguest.c:1026: warning: implicit declaration of function 'eventfd' make[1]: *** [lguest] Error 1 make[1]: Leaving directory `/usr/src/linux-2.6.35-rc6/Documentation/lguest' make: *** [debian/stamp/build/kernel] Error 2 ========== - -- Those who torment us for our own good will torment us without end, for they do so with the approval of their consciences. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iQEVAwUBTExlkC9Y35yItIgBAQIkZQf/XJqNfWBom12LWS6mBIM1aBjjoQaDBFlv cTCZoMbPlnkVZiq8QokP3PL+ChPTmf63NV3grbUNKSfDMPADrNhhs0OsjBDbY5zd DDoga+1wIUwTMwCiNH1McqFM682R36Z9SwqdJOCU1Cii8aBwQ7IchcJP8dGU9+3+ SUVnlprhsXTYsTNHxa8+0AiZPOdkSWCotii26Mo4ljeaIgCiTmCahD9nLiLt9OOw VnkiE0OWHDybZ4JK6JDHYK67Gk6xIUSvndUYIhjYAgxuh9TCicaxn2LrWagwScCH sMxYVtmGP0iHz41kP1daSpYiHbvMlpZHxdt00TGQnR3yWAoIeRBapA== =4oN7 -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to debian-user-REQUEST(a)lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org Archive: http://lists.debian.org/201007251225.52779.Howland(a)priss.com
First
|
Prev
|
Next
|
Last
Pages: 1 2 3 4 5 Prev: wifi gets disconnected frequently Next: unbelievable, #$@%%!! grub breaks for me AGAIN |