From owner-freebsd-hackers Fri May 2 19:09:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA05816 for hackers-outgoing; Fri, 2 May 1997 19:09:28 -0700 (PDT) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA05810 for ; Fri, 2 May 1997 19:09:22 -0700 (PDT) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 1.60 #1) id 0wNUFJ-0006tY-00; Fri, 2 May 1997 20:08:21 -0600 To: Terry Lambert Subject: Re: make flags Cc: bsdhack@shadows.aeon.net (mika ruohotie), hackers@freebsd.org In-reply-to: Your message of "Fri, 02 May 1997 14:00:08 PDT." <199705022100.OAA09474@phaeton.artisoft.com> References: <199705022100.OAA09474@phaeton.artisoft.com> Date: Fri, 02 May 1997 20:08:21 -0600 From: Warner Losh Message-Id: Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199705022100.OAA09474@phaeton.artisoft.com> Terry Lambert writes: : The makefiles must be "-j" aware. Alternatively, -j 2 could be added to the MAKE make macro, which would help a lot. Currently, it isn't added. However, things like -k are. Go figure. : All in all, I don't think you'd get much of a win from anything : other than -current with the changes in place. In build libc with -j 2 and w/o I found that it was faster on my PPro 200 to do it w/o the flag. I got 99% CPU without the flag, and 87% CPU with the flag. Maybe I'm a mutant :-) Warner