From owner-freebsd-questions Tue Nov 7 3:54:22 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail-1.sjc.telocity.net (mail-1.sjc.telocity.net [216.227.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 87E7737B479; Tue, 7 Nov 2000 03:54:13 -0800 (PST) Received: from zoso (dsl-216-227-91-85.telocity.com [216.227.91.85]) by mail-1.sjc.telocity.net (8.9.3/8.9.3) with SMTP id DAA18895; Tue, 7 Nov 2000 03:52:01 -0800 (PST) From: "Otter" To: "Roman Shterenzon" , "Makoto MATSUSHITA" Cc: , Subject: RE: We cannot use 'make -j' option to build the world, period. Date: Tue, 7 Nov 2000 06:57:11 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding the -j option, I seem to remember someone telling me that option was only for make buildworld/installworld and not the modules or anything else. Anyone care to confirm and/or explain why? I see the following in the man page: The options are as follows: -B Try to be backwards compatible by executing a single shell per command and by executing the commands to make the sources of a dependency line in sequence. This is turned on by default unless -j is used. -j max_jobs Specify the maximum number of jobs that make may have running at any one time. Turns compatibility mode off, unless the B flag is also specified. -Otter }-----Original Message----- }From: owner-freebsd-stable@FreeBSD.ORG }[mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Roman }Shterenzon }Sent: Monday, November 06, 2000 7:53 AM }To: Makoto MATSUSHITA }Cc: stable@FreeBSD.ORG }Subject: Re: We cannot use 'make -j' option to build the }world, period. } } }I've done make -j 3 buildworld couple of days ago and it worked fine. }Just my 0.02$ } }On Sat, 4 Nov 2000, Makoto MATSUSHITA wrote: } }> }> matusita> I've found that current src/sys/modules/linux }for RELENG_4 }> matusita> is not 'make -j' safe. It maybe causes a problem }if you want }> matusita> to make a module. }> }> Long time has past and, but problem is still there. }> }> OK, we all FreeBSD users should forget the fact that there is an }> option '-j' in make(1) and it's helpful for building }FreeBSD. I dunno }> what it should be, but 'linux' modules breaks the existing }situation. }> Documentation team, you should delete some comments of }this option in }> cutting-edge/chapter.sgml. }> }> Moreover, I've found that exactly the same problem is also }in latest }> 5-current (I've tested with 'make -j 2'). Be careful that some }> programs are called twice. }> }> ===> linux }> @ -> /usr/src/sys }> machine -> /usr/src/sys/i386/include }> echo "#define COMPAT_43 1" > opt_compat.h }> touch opt_linux.h }> touch opt_vmpage.h }> perl @/kern/vnode_if.pl -h @/kern/vnode_if.src }> sh @/kern/makesyscalls.sh @/i386/linux/syscalls.master }@/i386/linux/syscalls.cof }> sh @/kern/makesyscalls.sh @/i386/linux/syscalls.master }@/i386/linux/syscalls.cof }> sed -e 's|i386/linux/linux_proto\.h|linux_proto.h|g' }linux_sysent.c > linux_sysnt.c.fixup }> sed -e 's|i386/linux/linux_proto\.h|linux_proto.h|g' }linux_sysent.c > linux_sysnt.c.fixup }> mv -f linux_sysent.c.fixup linux_sysent.c }> mv -f linux_sysent.c.fixup linux_sysent.c }> cc -c -O -pipe -D_KERNEL -Wall -Wredundant-decls }-Wnested-externs -Wstrict-prottypes -Wmissing-prototypes }-Wpointer-arith -Winline -Wcast-qual -fformat-extenions }-ansi -DKLD_MODULE -nostdinc -I- -I. -I@ -I@/../include }-I/usr/include -preferred-stack-boundary=2 }/usr/src/sys/modules/linux/../../i386/linux/linux_genssym.c }> mv: rename linux_sysent.c.fixup to linux_sysent.c: No such }file or directory }> *** Error code 1 }> 1 error }> *** Error code 2 }> 1 error }> *** Error code 2 }> 1 error }> *** Error code 2 }> }> Stop in /usr/src/release. }> }> *** }> }> for current@freebsd.org (or hosokawa-san) only: }> }> There is yet another compilation problem in kernel }modules. A logfile }> attached below comes from 'createBOOTMFS' stage of }src/release/Makefile }> }> rm -f .depend }> mv -f .newdep .depend }> cd ../../modules && env }MAKEOBJDIRPREFIX=/usr/src/sys/compile/BOOTMFS/modules }KMODIR= make obj all }> ===> 3dfx }> ===> 3dfx }> Warning: Object directory not changed from original }/usr/src/sys/modules/3dfx }> @ -> /usr/src/sys }> machine -> /usr/src/sys/i386/include }> }/usr/src/sys/compile/BOOTMFS/modules/usr/src/sys/modules/3dfx } created for /usr/sr/sys/modules/3dfx }> }> Be careful, '3dfx' directory is called twice, and one of }them doesn't }> know that there is an obj/ directory. Maybe it is introduced by the }> changes of cool and long-awaited feature of driver.conf. }> }> -- - }> Makoto `MAR' MATSUSHITA }> }> }> To Unsubscribe: send mail to majordomo@FreeBSD.org }> with "unsubscribe freebsd-stable" in the body of the message }> } }--Roman Shterenzon, UNIX System Administrator and Consultant }[ Xpert UNIX Systems Ltd., Herzlia, Israel. Tel: +972-9-9522361 ] } } } }To Unsubscribe: send mail to majordomo@FreeBSD.org }with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message