Date: Tue, 9 Dec 2003 22:26:47 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: current@freebsd.org Subject: Re: buildworld problem with -CURRENT as of a half hour ago Message-ID: <20031210042647.GE2435@dan.emsphone.com> In-Reply-To: <20031210035903.GA2174@troutmask.apl.washington.edu> References: <20031210023632.GA13539@afflictions.org> <mailman.1071024061.20138.fcurrent-l@lists.sentex.ca> <20031210024302.GB13539@afflictions.org> <20031210035903.GA2174@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Dec 09), Steve Kargl said: > On Tue, Dec 09, 2003 at 09:43:02PM -0500, Damian Gerow wrote: > > Thus spake Steve Kargl (sgk@troutmask.apl.washington.edu) [09/12/03 21:38]: > > : On Tue, Dec 09, 2003 at 09:36:32PM -0500, Damian Gerow wrote: > > : > /usr/obj/usr/src/i386/usr/lib/libtinfo_p.a -> libncurses_p.a > > : > 1 error > > : > *** Error code 2 > > : > > > : > It's not even clear what the error is -- it just says 'error'. > > : > Scrolling back up through my buffer doesn't show anything at > > : > all. > > : > > : Are you using "make -j 4"? > > > > I'd tried 'make -j4' and 'make -j2', don't remember if I did a > > straight buildworld or not -- just trying again now, it'll be about > > 15-20 minutes before I can tell for sure. > > > > And yes, both -j4 and -j2 resulted in the same error. > > -j# obfuscates where the actual error occurs unless you have enough > make-fu to read the log. The first step one should take when this > type of error happens is a plain "make buildworld". You can usually do a "make -DNOCLEAN buildworld" here to speed up the run. It'll zip through what you've already compiled rather than rebuild it. If this build succeeds, there's probably a dependency problem someplace causing the -j build to fail. Also logging your builds is a good idea: "script world.log make -j4 buildworld". > The next step is run cvsup again to see if the problem has > been fixed. Then, report the error to freebsd-current. -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031210042647.GE2435>