At 12:38 PM -0400 9/15/01, Mike Tancsa wrote:
>Should a parallel build always work ? I was just trying to stress
>a new series of MB we are evaluating and to my suprise, -j4 works,
>but not -j8
Well, in a philosophical sense, yes it "should" always work. Bugs
creep into the process from time-to-time. I can not say that I
know how to pin down such problems when they occur. I do know
that earlier this year I had some problem I was checking, and as
a tangent to that problem I did several fresh 'make buildworld's,
going from -j2 to -j10 on my dual 650-MHz pentium machine. I then
did md5 comparisons of the resulting obj-tree results, and they all
came out the same. Of course, I wasn't getting any errors at build
time, either.
What happens if you remove all of /usr/obj/usr/src before trying
to build with -j8?
>===> usr.sbin/boot0cfg
>rm -f .depend
>mkdep -f .depend -a -I/usr/obj/usr/src/i386/usr/include
>/usr/src/usr.sbin/boot0cfg/boot0cfg.c
>cd /usr/src/usr.sbin/boot0cfg; make _EXTRADEPEND
>echo boot0cfg: /usr/obj/usr/src/i386/usr/lib/libc.a >> .depend
>1 error
>*** Error code 2
>1 error
>*** Error code 2
the thing which interests me about the above is that 'make' aborts
with "error code 2", but I don't see any error message as to what the
error was. I wonder if this is another case in "/bin/sh -e" where an
error return is NOT being ignored when it should be ignored. I fixed
two similar bugs last summer last summer.
[aside on those multiple builds that I did: It was interesting that
even though it was on a dual-processor system, there was not much of
a speed improvement (on 4.3-stable) when going from -j4 to -j10. Big
improvement going from -j1 to -j4, but after that it didn't help much]
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message