Re: Buildworld fails in 5.1-CURRENT in wall- SOLVED
Dag-Erling Smørgrav wrote: "M. Warner Losh" <[EMAIL PROTECTED]> writes: find /usr/obj -name .depend or better yet rm -rf /usr/obj/* *ahem* the correct incantation is: # cd /usr/src # make cleandir # make cleandir DES Removing the /usr/obj/* tree worked, back in business. Will have to take a closer look at the 'master' Makefile, as I didn't see the cleandir target at first glance, so had been using 'make clean && make buildworld' for previous builds- I take it this is NOT needed as the build process does a 'make clean' prior to building? Thanks to all... Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1-CURRENT in wall
"M. Warner Losh" <[EMAIL PROTECTED]> writes: > find /usr/obj -name .depend > > or better yet > > rm -rf /usr/obj/* *ahem* the correct incantation is: # cd /usr/src # make cleandir # make cleandir DES -- Dag-Erling Smørgrav - [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1-CURRENT in wall
M. Warner Losh wrote: In message: <[EMAIL PROTECTED]> Scott W <[EMAIL PROTECTED]> writes: : M. Warner Losh wrote: : : >I'd remove all the .depend files and try again. : > : >Warner : >___ : >[EMAIL PROTECTED] mailing list : >http://lists.freebsd.org/mailman/listinfo/freebsd-current : >To unsubscribe, send any mail to "[EMAIL PROTECTED]" : > : > : > : I've tried that one- I'm not familiar with freeBSD's build environment, : but 'find /usr/src -name ".depend" shows the only .depend files are in : the kernel tree /usr/src/sus/i386/compile/ , so I'm assuming it's : generating them as part of the build process itself, or dumping them : outside of the /usr/src heirarchy. Tried again from cvsup ~11pm with : same results...any other ideas? find /usr/obj -name .depend or better yet rm -rf /usr/obj/* Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" D'oh! Got it, trying now.. thanks! :-) Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1-CURRENT in wall
In message: <[EMAIL PROTECTED]> Scott W <[EMAIL PROTECTED]> writes: : M. Warner Losh wrote: : : >I'd remove all the .depend files and try again. : > : >Warner : >___ : >[EMAIL PROTECTED] mailing list : >http://lists.freebsd.org/mailman/listinfo/freebsd-current : >To unsubscribe, send any mail to "[EMAIL PROTECTED]" : > : > : > : I've tried that one- I'm not familiar with freeBSD's build environment, : but 'find /usr/src -name ".depend" shows the only .depend files are in : the kernel tree /usr/src/sus/i386/compile/ , so I'm assuming it's : generating them as part of the build process itself, or dumping them : outside of the /usr/src heirarchy. Tried again from cvsup ~11pm with : same results...any other ideas? find /usr/obj -name .depend or better yet rm -rf /usr/obj/* Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1-CURRENT in wall
M. Warner Losh wrote: I'd remove all the .depend files and try again. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]" I've tried that one- I'm not familiar with freeBSD's build environment, but 'find /usr/src -name ".depend" shows the only .depend files are in the kernel tree /usr/src/sus/i386/compile/ , so I'm assuming it's generating them as part of the build process itself, or dumping them outside of the /usr/src heirarchy. Tried again from cvsup ~11pm with same results...any other ideas? Scott ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1-CURRENT in wall
I'd remove all the .depend files and try again. Warner ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
In message: <[EMAIL PROTECTED]> Tim Kientzle <[EMAIL PROTECTED]> writes: : Gordon Tetlow wrote: : > On Mon, Jul 21, 2003 at 09:36:37AM -0700, Tim Kientzle wrote: : >>Hmmm... Is that what .ORDER is for? To work around a : >>parallel make that gratuitously rebuilds things? : > : > Right it serializes build dependencies. The problem with crunchgen ... : : I would argue "the problem with make"... ;-) I think it's pretty : clear that : : a b c: foo : buildabc : : does not require that 'buildabc' be run three times. Make : should be able to note that 'buildabc' was already spawned : for 'a' and just add 'b' and 'c' to the wait list for : that operation, rather than running additional copies. That's not how make works. a b c: foo buildabc is the same as: a: foo buildabc b: foo buildabc c: foo buildabc ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Mon, Jul 21, 2003 at 09:46:03AM -0700, Tim Kientzle wrote: > Gordon Tetlow wrote: > >On Mon, Jul 21, 2003 at 09:36:37AM -0700, Tim Kientzle wrote: > >>Hmmm... Is that what .ORDER is for? To work around a > >>parallel make that gratuitously rebuilds things? > > > >Right it serializes build dependencies. The problem with crunchgen ... > > I would argue "the problem with make"... ;-) I think it's pretty > clear that It is not clear. > a b c: foo > buildabc > > does not require that 'buildabc' be run three times. The above is short hand for a: foo buildabc b: foo buildabc c: foo buildabc make in no way knows that buildabc produces 3 things and not a single one. -- -- David ([EMAIL PROTECTED]) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Mon, Jul 21, 2003 at 09:46:03AM -0700, Tim Kientzle wrote: > > I would argue "the problem with make"... ;-) I think it's pretty > clear that > > a b c: foo > buildabc > > does not require that 'buildabc' be run three times. It's a common perception and one that's wrong. a b c: d foo is a shorthand for a: d foo b: d foo c: d foo Since most make variants only look at the timestamp one can avoid building a, b, and c thrice by enforcing an ordering. Make variants like clearmake may not be tricked that easily, because they keep track of much more. -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
At 9:46 AM -0700 7/21/03, Tim Kientzle wrote: Gordon Tetlow wrote: On Mon, Jul 21, 2003, Tim Kientzle wrote: Hmmm... Is that what .ORDER is for? To work around a parallel make that gratuitously rebuilds things? Right it serializes build dependencies. The problem with crunchgen ... I would argue "the problem with make"... ;-) I think it's pretty clear that a b c: foo buildabc does not require that 'buildabc' be run three times. Make should be able to note that 'buildabc' was already spawned for 'a' and just add 'b' and 'c' to the wait list for that operation, rather than running additional copies. It may not be quite that simple, when it gets to splitting apart the make rules to build things in parallel. I tracked down two problems with parallel builds, and in both cases make was "doing the right thing", given the rules that it was working with. On the other hand, I'm certainly no expert when it comes to writing makefiles for parallel builds. In any case, the suggested change did not solve the problem for me, when doing a make -j5 buildworld. I still get the failure with: make: don't know how to make /usr/obj/usr/src/rescue/rescue//usr/src/sbin/dhclie nt/client/clparse.o. Stop If there's some other way I should run the buildworld to generate a more helpful output, let me know. The failure seems to be 100% reproducible on my machine, at least if I start out by removing all of /usr/obj/usr/src. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
Gordon Tetlow wrote: On Mon, Jul 21, 2003 at 09:36:37AM -0700, Tim Kientzle wrote: Hmmm... Is that what .ORDER is for? To work around a parallel make that gratuitously rebuilds things? Right it serializes build dependencies. The problem with crunchgen ... I would argue "the problem with make"... ;-) I think it's pretty clear that a b c: foo buildabc does not require that 'buildabc' be run three times. Make should be able to note that 'buildabc' was already spawned for 'a' and just add 'b' and 'c' to the wait list for that operation, rather than running additional copies. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Mon, Jul 21, 2003 at 09:36:37AM -0700, Tim Kientzle wrote:
> Gordon Tetlow wrote:
> >It seems that the $(OUTPUTS) target (which has 3 components) causes
> >this particular error.
> >
> >+.ORDER: $(OUTPUTS)
> > $(OUTPUTS): $(CONF)
> >MAKEOBJDIRPREFIX=${CRUNCHOBJS} crunchgen -q -m $(OUTMK) -c $(OUTC)
> >\
> >$(CONF)
>
> Hmmm... Is that what .ORDER is for? To work around a
> parallel make that gratuitously rebuilds things?
Right it serializes build dependencies. The problem with crunchgen is
that a single command makes all of the OUTPUTS, so normally make will
spawn off the same command 3 times in parallel (which seems to cause
problems). To get around it, make it so you each of the OUTPUTS is
built in order and what occurs is a single crunchgen invocation that
the sees that the other OUTPUT targets are up-to-date and then
contintues along.
> >After doing that, I run into a problem with clparse.o from the dhclient
> >build. I think I might have a solution for that, but I'm too tired
> >right now to think straight. I'll look at it tomorrow.
>
>
> A-ha! I've known that dhclient was a problem, but the
> above gives me an idea. I wonder if the following helps?
I'll give it a whirl.
-gordon
pgp0.pgp
Description: PGP signature
Re: Buildworld fails in 5.1
Gordon Tetlow wrote:
It seems that the $(OUTPUTS) target (which has 3 components) causes
this particular error.
+.ORDER: $(OUTPUTS)
$(OUTPUTS): $(CONF)
MAKEOBJDIRPREFIX=${CRUNCHOBJS} crunchgen -q -m $(OUTMK) -c $(OUTC) \
$(CONF)
Hmmm... Is that what .ORDER is for? To work around a
parallel make that gratuitously rebuilds things?
After doing that, I run into a problem with clparse.o from the dhclient
build. I think I might have a solution for that, but I'm too tired
right now to think straight. I'll look at it tomorrow.
A-ha! I've known that dhclient was a problem, but the
above gives me an idea. I wonder if the following helps?
Tim
Index: sbin/dhclient//Makefile
===
RCS file: /usr/cvs/FreeBSD-CVS/src/sbin/dhclient/Makefile,v
retrieving revision 1.20
diff -u -r1.20 Makefile
--- sbin/dhclient/Makefile 29 Jun 2003 18:46:17 - 1.20
+++ sbin/dhclient/Makefile 21 Jul 2003 16:34:22 -
@@ -52,6 +52,8 @@
# though, so we must run ``make all'' instead when we are asked to
# generate an individual object file.
+.ORDER: $(OBJS)
+
# Note: Must have some commands here to override the default build action
${OBJS}: all
@true
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
At 12:34 AM -0400 7/21/03, Garance A Drosihn wrote: I do know that buildworld finishes OK if I define NORESCUE. Right now I am running a buildworld that does not specify -j, and I'll see if that completes OK. The buildworld without -j did successfully complete. I have added that logfile to the lines in ~gad/rescueb if anyone wants to look at them. All of these builds were with -current as of Friday. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Fri, Jul 18, 2003 at 11:39:53AM -0700, Tim Kientzle wrote:
>
> I wrote the /rescue stuff and a lot of people have
> reported that it breaks parallel builds, but I haven't yet
> come up with anything. (In part, because I haven't yet
> managed to reproduce it. )
>
> A couple of things look odd about this:
>
> 1) You should not be building 'rescue.mk' twice.
>That could be the problem right there, if the rescue.mk
>makefile is getting rebuilt (overwritten) while another
>build thread is using it. The dependencies in
>rescue/rescue/Makefile look right to me, but I
>could be missing something.
It seems that the $(OUTPUTS) target (which has 3 components) causes
this particular error. It can be easily avoided with the following
patch (against an older version of src/rescue/rescue/Makefile,
should be fine):
(Whitespace is probably messed up)
//depot/user/gordon/dynamic/src/rescue/rescue/Makefile#7 - /home/gtetlow/p4
/dynamic/src/rescue/rescue/Makefile
@@ -244,6 +244,7 @@
.endfor
+.ORDER: $(OUTPUTS)
$(OUTPUTS): $(CONF)
MAKEOBJDIRPREFIX=${CRUNCHOBJS} crunchgen -q -m $(OUTMK) -c $(OUTC) \
$(CONF)
After doing that, I run into a problem with clparse.o from the dhclient
build. I think I might have a solution for that, but I'm too tired
right now to think straight. I'll look at it tomorrow.
-gordon
pgp0.pgp
Description: PGP signature
Re: Buildworld fails in 5.1
At 9:48 PM -0400 7/20/03, Matt Loschert wrote: On Fri, 18 Jul 2003, Tim Kientzle wrote: > Crunchgen writes out and runs a short makefile in order to grab build information from a particular program. Since /rescue has about 120 components, you should see 'crunchgen_objs' and 'loop' targets getting built about 120 times. Ummm... by '363 times', did you mean 363 lines or 363 copies of this six-line block? If the latter, then something is definitely getting rebuilt needlessly. That whole block of 6 lines is getting written 363 times. IIRC, I grepped for 'Results of making crunchgen_objs' in the build logs. The failure that I am seeing is different than the above failure. I have a dual-CPU system, and have done buildworlds with -j5, -j4, and -j3. All of them fail with an error somewhere in 'rescue' building. None of them have *any* lines about 'Results of making crunchgen_objs'. There is some make-related error messages in the midst of building rescue, and then more standard 'cc' commands unrelated to rescue (which worked), and then buildworld fails. Well, the -j2 build also just finished with an error. The logfiles I keep are in the directory: ~gad/rescueb on freefall.freebsd, as gzip'ed files. The output is altered a little bit due to a script that I use to keep track of warning and error messages, but it is not altered much. The most notable difference is that at the end of the build it gives a summary of the # of warning messages that were generated. It may also be significant that I started out all of these buildworlds by first: rm -rf /usr/obj/usr/src/* so buildworld would have had to build *everything*. I do know that buildworld finishes OK if I define NORESCUE. Right now I am running a buildworld that does not specify -j, and I'll see if that completes OK. However, I have to leave for home now, so I'll have to finish that when I get back in on Monday. -- Garance Alistair Drosehn= [EMAIL PROTECTED] Senior Systems Programmer or [EMAIL PROTECTED] Rensselaer Polytechnic Instituteor [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Fri, 18 Jul 2003, Tim Kientzle wrote: > Tim Kientzle wrote: > > Matt Loschert wrote: > >> Then the following output repeated 363 times > >> > >> > >> crunchgen: make error: Remaking `crunchgen_objs' > >> > >> crunchgen: make error: Results of making crunchgen_objs: > >> > >> crunchgen: make error: > >> > >> crunchgen: make error: Remaking `loop' > >> > >> crunchgen: make error: Results of making loop: > >> > >> crunchgen: make error: > > A little more information: > > The word 'error' here concerns me, but > the repetition is expected. > Crunchgen writes out and runs a short makefile > in order to grab build information from a particular > program. Since /rescue has about 120 components, > you should see 'crunchgen_objs' and 'loop' targets > getting built about 120 times. > > Ummm... by '363 times', did you mean 363 lines or > 363 copies of this six-line block? If the latter, > then something is definitely getting rebuilt > needlessly. That whole block of 6 lines is getting written 363 times. IIRC, I grepped for 'Results of making crunchgen_objs' in the build logs. > Tim Again, I will email you the full logs in the morning. That will probably help you more. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Fri, 18 Jul 2003, Tim Kientzle wrote: > Matt Loschert wrote: > > After grepping through the build log > > for error messages, I found the following output, which appears to be some > > sort of build loop gone wild: > > > > First this > > -- > > Results of making rescue.cache: > > MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c > > rescue.c rescue.conf > > > > > > Then the following output repeated 363 times > > > > > > crunchgen: make error: Remaking `crunchgen_objs' > > > > crunchgen: make error: Results of making crunchgen_objs: > > > > crunchgen: make error: > > > > crunchgen: make error: Remaking `loop' > > > > crunchgen: make error: Results of making loop: > > > > crunchgen: make error: > > > > > > With the following output repeated 2 times within the above output > > -- > > > > Run "make -f rescue.mk" to build crunched binary. > > *** Error code 1 > > Results of making rescue.mk: > > MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c > > rescue.c rescue.conf > > > > > > I suppose this means that there is a dependency missing for the rescue > > crunchgen target? > > Good work, Matt. > > I wrote the /rescue stuff and a lot of people have > reported that it breaks parallel builds, but I haven't yet > come up with anything. (In part, because I haven't yet > managed to reproduce it. ) > > A couple of things look odd about this: > > 1) You should not be building 'rescue.mk' twice. > That could be the problem right there, if the rescue.mk > makefile is getting rebuilt (overwritten) while another > build thread is using it. The dependencies in > rescue/rescue/Makefile look right to me, but I > could be missing something. > > 2) I can't find the 'crunchgen_objs' or 'loop' > targets offhand. I'm doing a more extensive > find/grep search right now to see if I can figure > out where those are coming from. > > Somewhere in here is the answer to this problem, > I just don't see it yet. > > Tim Kientzle > > P.S. Could you email me the log from your build > that failed? Sure. I have it on one of my machines at work. I will email it to you on Monday morning.. > Could you try a lower -j value? If -j 2 fails, > for instance, that might be easier to diagnose. > Thanks for all your help. Definitely, I will fire off a build when I get in on Monday. Thanks, - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
Tim Kientzle wrote: Matt Loschert wrote: Then the following output repeated 363 times crunchgen: make error: Remaking `crunchgen_objs' crunchgen: make error: Results of making crunchgen_objs: crunchgen: make error: crunchgen: make error: Remaking `loop' crunchgen: make error: Results of making loop: crunchgen: make error: A little more information: The word 'error' here concerns me, but the repetition is expected. Crunchgen writes out and runs a short makefile in order to grab build information from a particular program. Since /rescue has about 120 components, you should see 'crunchgen_objs' and 'loop' targets getting built about 120 times. Ummm... by '363 times', did you mean 363 lines or 363 copies of this six-line block? If the latter, then something is definitely getting rebuilt needlessly. Tim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
Matt Loschert wrote: After grepping through the build log for error messages, I found the following output, which appears to be some sort of build loop gone wild: First this -- Results of making rescue.cache: MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf Then the following output repeated 363 times crunchgen: make error: Remaking `crunchgen_objs' crunchgen: make error: Results of making crunchgen_objs: crunchgen: make error: crunchgen: make error: Remaking `loop' crunchgen: make error: Results of making loop: crunchgen: make error: With the following output repeated 2 times within the above output -- Run "make -f rescue.mk" to build crunched binary. *** Error code 1 Results of making rescue.mk: MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf I suppose this means that there is a dependency missing for the rescue crunchgen target? Good work, Matt. I wrote the /rescue stuff and a lot of people have reported that it breaks parallel builds, but I haven't yet come up with anything. (In part, because I haven't yet managed to reproduce it. ) A couple of things look odd about this: 1) You should not be building 'rescue.mk' twice. That could be the problem right there, if the rescue.mk makefile is getting rebuilt (overwritten) while another build thread is using it. The dependencies in rescue/rescue/Makefile look right to me, but I could be missing something. 2) I can't find the 'crunchgen_objs' or 'loop' targets offhand. I'm doing a more extensive find/grep search right now to see if I can figure out where those are coming from. Somewhere in here is the answer to this problem, I just don't see it yet. Tim Kientzle P.S. Could you email me the log from your build that failed? Could you try a lower -j value? If -j 2 fails, for instance, that might be easier to diagnose. Thanks for all your help. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, Jul 16, 2003 at 02:24:18PM +, Bosko Milekic wrote: > > Same here, remove the -j N. Right now there seem to be some > dependencies which you fail against with a parallel build. And it works here as well. Building with -j highlights a problem I'm seeing on a sparc64 though ... the stock Ultra 5 hard drive is abysmally slow. Bonnie++ reports: Version 1.93c --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP Caliban512M 8 95 1995 10 927 515 94 1893 6 54.9 17 Latency 1878ms 445ms2894ms1074ms 272ms5349ms Version 1.93c --Sequential Create-- Random Create Caliban -Create-- --Read--- -Delete-- -Create-- --Read--- -Delete-- files /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP /sec %CP 16 918 72 3008 82 2649 97 697 55 3112 89 2825 97 Latency 1665ms 51352us2797us1622ms 345ms2241us Compare this to a NFS mount (with options rw, intr, nfsv3, -w=32768, -r=32768) on the same box (an Ultra 5) from my vinum fileserver: Version 1.93c --Sequential Output-- --Sequential Input- --Random- Concurrency 1 -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- MachineSize K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP Caliban512M4076 18 1764 174102 15 79.5 77 Latency 294ms 184ms 44630us1699ms This made the buildworld time /really/ slow: real1068m1.246s user904m49.768s sys 80m51.158s (buildkernel took about an additional ten hours). I'm hoping that replacing it with a more modern hard-drive should fix this, though I'll be poking through atacontrol and dmesg to see if it's a simple configuration problem. In the meantime it's actually faster for me to build off of an NFS mount. Heh. -T -- Page 461: Tools that are simple enough to use the first day are often a real pain after the first month. - Harley Hahn, _The Unix Companion_ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Fri, 18 Jul 2003, Bruce Evans wrote: > On Thu, 17 Jul 2003, Matt Loschert wrote: > > > On Thu, 17 Jul 2003, Bruce Evans wrote: > > > Try using make -P to unmix the output... > > > > I am not sure if this is useful or not, but I took your suggestion of > > using make -P, and now the build stops with the following output: > > > > ... > > Remaking `fdisk' > > Results of making fdisk: > > cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -W > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -static -o > > fdisk fdisk.o geom_mbr_enc.o > > 1 error > > *** Error code 2 > > Unfortunately, the critical error message still seems to be elsewhere. I > think the error is not associated with fdisk (although it immediately > follows the fdisk results) since cc would have printed a message if it > (cc) failed. > > Bruce Bruce, Thanks for the information, it prompted me to look harder. I am not sure, but I may have found the problem. After grepping through the build log for error messages, I found the following output, which appears to be some sort of build loop gone wild: First this -- Results of making rescue.cache: MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf Then the following output repeated 363 times crunchgen: make error: Remaking `crunchgen_objs' crunchgen: make error: Results of making crunchgen_objs: crunchgen: make error: crunchgen: make error: Remaking `loop' crunchgen: make error: Results of making loop: crunchgen: make error: With the following output repeated 2 times within the above output -- Run "make -f rescue.mk" to build crunched binary. *** Error code 1 Results of making rescue.mk: MAKEOBJDIRPREFIX=/usr/obj/usr/src/rescue/rescue crunchgen -q -m rescue.mk -c rescue.c rescue.conf I suppose this means that there is a dependency missing for the rescue crunchgen target? - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Thu, 17 Jul 2003, Matt Loschert wrote: > On Thu, 17 Jul 2003, Bruce Evans wrote: > > Try using make -P to unmix the output... > > I am not sure if this is useful or not, but I took your suggestion of > using make -P, and now the build stops with the following output: > > ... > Remaking `fdisk' > Results of making fdisk: > cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -W > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual > -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -static -o fdisk > fdisk.o geom_mbr_enc.o > 1 error > *** Error code 2 Unfortunately, the critical error message still seems to be elsewhere. I think the error is not associated with fdisk (although it immediately follows the fdisk results) since cc would have printed a message if it (cc) failed. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Bosko Milekic smacked into the keyboard: > > Same here, remove the -j N. Right now there seem to be some > dependencies which you fail against with a parallel build. Yep this fixed it for me too, I was running -j4 (it's a 266, can't handle a whole lot) Thanks for the suggestion. static > Sorry for the top-posting. > > -Bosko > > On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: > > On Tue, 15 Jul 2003, Static wrote: > > > > > Just installed 5.1 yesterday, cvsuped using the . tag, and src-all > > > /etc/make.conf untouched. I attempted to buildworld and I get the following > > > > > > ranlib libc_pic.a > > > ranlib libc.a > > > ranlib libc_p.a > > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc.a > > > /usr/obj/usr/sr > > > c/i386/usr/lib > > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc_p.a > > > /usr/obj/usr/ > > > src/i386/usr/lib > > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libc.so.5 > > > /usr/obj/u > > > sr/src/i386/usr/lib > > > ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so > > > sh /usr/src/tools/install.sh -o root -g wheel -m 444 libc_pic.a > > > /usr/obj/usr/s > > > rc/i386/usr/lib > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > *** Error code 2 > > > 1 error > > > > > > Did not see an open pr or anything mentioned in mailing lists. Is this a > > > known issue and should I file a pr, or is there a hack/workaround to fix > > > this? > > > > > > Thanks > > > > > > rwz > > > > Static, > -- > Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED] > TECHNOkRATIS Consulting Services * http://www.technokratis.com/ > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Thu, 17 Jul 2003, Bruce Evans wrote: > On Wed, 16 Jul 2003, Dan Nelson wrote: > > > If you are using -j6, the real error could be many many lines above > > what you pasted. It's most likely in usr.sbin somewhere, but probably > > not keyserv. You'll have to capture the entire log and look at it to > > determine the first failure. > > Try using make -P to unmix the output. I don't know how well this > works in practice. This flag seems to be quite broken -- it causes > the (standard) output to be spammed with messages like > "Remaking (sic) foo.o" and "Results of making foo.o" even when make > is requested to be quiet (make -s) and the results are null. > > Using -P also has the side effect of accidentally avoiding the > longstanding bug of waiting for a select timeout for up to 100 msec > after each batch of jobs. > > Bruce Bruce, I am not sure if this is useful or not, but I took your suggestion of using make -P, and now the build stops with the following output: ===> sbin/cxconfig Remaking `cxconfig.o' Remaking `cxconfig.8.gz' Results of making cxconfig.8.gz: gzip -cn /usr/src/sbin/cxconfig/cxconfig.8 > cxconfig.8.gz Results of making cxconfig.o: cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -c /usr/src/sbin/cxconfig/cxconfig.c Remaking `cxconfig' Results of making cxconfig: cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -static -o cxconfig cxconfig.o ===> sbin/fdisk Remaking `fdisk.o' Remaking `geom_mbr_enc.o' Remaking `fdisk.8.gz' Results of making fdisk.8.gz: gzip -cn /usr/src/sbin/fdisk/fdisk.8 > fdisk.8.gz Results of making geom_mbr_enc.o: cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/sys/geom/geom_mbr_enc.c Results of making fdisk.o: cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -c /usr/src/sbin/fdisk/fdisk.c Remaking `fdisk' Results of making fdisk: cc -O -pipe -mcpu=pentiumpro-Wsystem-headers -Werror -Wall -Wno-format-y2k -W -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wcast-align -Wno-uninitialized -static -o fdisk fdisk.o geom_mbr_enc.o 1 error *** Error code 2 1 error *** Error code 2 1 error Again, I have full build logs if they would be useful to anyone. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Dan Nelson wrote: > If you are using -j6, the real error could be many many lines above > what you pasted. It's most likely in usr.sbin somewhere, but probably > not keyserv. You'll have to capture the entire log and look at it to > determine the first failure. Try using make -P to unmix the output. I don't know how well this works in practice. This flag seems to be quite broken -- it causes the (standard) output to be spammed with messages like "Remaking (sic) foo.o" and "Results of making foo.o" even when make is requested to be quiet (make -s) and the results are null. Using -P also has the side effect of accidentally avoiding the longstanding bug of waiting for a select timeout for up to 100 msec after each batch of jobs. Bruce ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Bosko Milekic wrote: > > Same here, remove the -j N. Right now there seem to be some > dependencies which you fail against with a parallel build. > > Sorry for the top-posting. > > -Bosko Bosko, That did the trick. Thanks so much. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Dan Nelson wrote: > In the last episode (Jul 16), Matt Loschert said: > > My buildworlds have been failing ever since the gcc 3.3 upgrade. I > > got the message that you got on one of the failures. However, my > > last three builds have consistently failed at the following point: > > > > ===> usr.sbin/keyserv > > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > > /usr/src/usr.sbin/keyserv/keyserv.c > > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > > /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 > > > keyserv.8.gz > > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c > > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > > /usr/src/usr.sbin/keyserv/crypt_server.c > > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv > > keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > > > My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. > > I am using a clean /usr/obj directory for each build. I am using -j 6 for > > the buildworld. Maybe that is the problems, I will try taking that out. > > If you are using -j6, the real error could be many many lines above > what you pasted. It's most likely in usr.sbin somewhere, but probably > not keyserv. You'll have to capture the entire log and look at it to > determine the first failure. > > -- > Dan Nelson > [EMAIL PROTECTED] Thanks Dan. I have the output saved, but I can't see anything obviously wrong. Bosko Milekic just emailed me too and said that there is currently a make dependency problem causing -j builds to fail. Beyond my make-foo skills. :) Anyway, my non-j build just finished successfully, so I guess that was it. BTW, if my build logs would be useful to anyone, I still have them. Thanks, - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
Same here, remove the -j N. Right now there seem to be some dependencies which you fail against with a parallel build. Sorry for the top-posting. -Bosko On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: > On Tue, 15 Jul 2003, Static wrote: > > > Just installed 5.1 yesterday, cvsuped using the . tag, and src-all > > /etc/make.conf untouched. I attempted to buildworld and I get the following > > > > ranlib libc_pic.a > > ranlib libc.a > > ranlib libc_p.a > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc.a > > /usr/obj/usr/sr > > c/i386/usr/lib > > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc_p.a > > /usr/obj/usr/ > > src/i386/usr/lib > > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libc.so.5 > > /usr/obj/u > > sr/src/i386/usr/lib > > ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so > > sh /usr/src/tools/install.sh -o root -g wheel -m 444 libc_pic.a > > /usr/obj/usr/s > > rc/i386/usr/lib > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > *** Error code 2 > > 1 error > > > > Did not see an open pr or anything mentioned in mailing lists. Is this a > > known issue and should I file a pr, or is there a hack/workaround to fix > > this? > > > > Thanks > > > > rwz > > Static, > > My buildworlds have been failing ever since the gcc 3.3 upgrade. I got > the message that you got on one of the failures. However, my last three > builds have consistently failed at the following point: > > ===> usr.sbin/keyserv > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/keyserv.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/setkey.c > gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 > keyserv.8.gz > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > crypt_svc.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/crypt_server.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o > keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto > -lrpcsvc > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > My make.conf is as follows: > > CFLAGS= -O -pipe > NOPROFILE= true > COPTFLAGS= -O -pipe > COMPAT3X= yes > COMPAT4X= yes > BOOTWAIT= 0 > USA_RESIDENT= YES > DOC_LANG= en_US.ISO8859-1 > PERL_VER= 5.8.0 > PERL_VERSION= 5.8.0 > PERL_ARCH= mach > NOPERL= yo > NO_PERL=yo > NO_PERL_WRAPPER=yo > > My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. > I am using a clean /usr/obj directory for each build. I am using -j 6 for > the buildworld. Maybe that is the problems, I will try taking that out. > > Anyway, I have not seen any mention on the lists of similar failures > either. There must be something funky that we are doing. > > - Matt > > -- > Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| > ServInt Internet Services | web: http://www.servint.net/ | > McLean, Virginia USA| phone: (703) 847-1381 | > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > -- Bosko Milekic * [EMAIL PROTECTED] * [EMAIL PROTECTED] TECHNOkRATIS Consulting Services * http://www.technokratis.com/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
In the last episode (Jul 16), Matt Loschert said: > My buildworlds have been failing ever since the gcc 3.3 upgrade. I > got the message that you got on one of the failures. However, my > last three builds have consistently failed at the following point: > > ===> usr.sbin/keyserv > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/keyserv.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 > > keyserv.8.gz > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c > /usr/src/usr.sbin/keyserv/crypt_server.c > cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv > keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. > I am using a clean /usr/obj directory for each build. I am using -j 6 for > the buildworld. Maybe that is the problems, I will try taking that out. If you are using -j6, the real error could be many many lines above what you pasted. It's most likely in usr.sbin somewhere, but probably not keyserv. You'll have to capture the entire log and look at it to determine the first failure. -- Dan Nelson [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, 16 Jul 2003, Tillman wrote: > On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: > > My buildworlds have been failing ever since the gcc 3.3 upgrade. I got > > the message that you got on one of the failures. However, my last three > > builds have consistently failed at the following point: > > Mine has as well, though I thought the issue was specific to sparc64 > (I'm on an Ultra 5). I cvsup'ed up again this morning and am trying > again with -jX. It'll take a while to find out as this box takes a long > time to compile recent -CURRENT. I'm currently 5 hours into buildworld > and it's on contrib/ncurses. > > > My make.conf is as follows: > > > > CFLAGS= -O -pipe > > NOPROFILE= true > > COPTFLAGS= -O -pipe > > COMPAT3X= yes > > COMPAT4X= yes > > BOOTWAIT= 0 > > USA_RESIDENT= YES > > Same compile options as me, though I don't have COMPAT or BOOTWAIT. > > > My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. > > I am using a clean /usr/obj directory for each build. I am using -j 6 for > > the buildworld. Maybe that is the problems, I will try taking that out. > > I'd be interested in seeing if that works for you - it'll be a few hours > before my run is finished so you'll know before I will ;-) > > -T Tillman, It takes 1 1/2 hours to hit the point of failure, so it will be a short while, but I will let you know. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Wed, Jul 16, 2003 at 01:47:38PM -0400, Matt Loschert wrote: > My buildworlds have been failing ever since the gcc 3.3 upgrade. I got > the message that you got on one of the failures. However, my last three > builds have consistently failed at the following point: Mine has as well, though I thought the issue was specific to sparc64 (I'm on an Ultra 5). I cvsup'ed up again this morning and am trying again with -jX. It'll take a while to find out as this box takes a long time to compile recent -CURRENT. I'm currently 5 hours into buildworld and it's on contrib/ncurses. > My make.conf is as follows: > > CFLAGS= -O -pipe > NOPROFILE= true > COPTFLAGS= -O -pipe > COMPAT3X= yes > COMPAT4X= yes > BOOTWAIT= 0 > USA_RESIDENT= YES Same compile options as me, though I don't have COMPAT or BOOTWAIT. > My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. > I am using a clean /usr/obj directory for each build. I am using -j 6 for > the buildworld. Maybe that is the problems, I will try taking that out. I'd be interested in seeing if that works for you - it'll be a few hours before my run is finished so you'll know before I will ;-) -T -- Do not consciously seek enlightenment. -Muso Kokushi ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Buildworld fails in 5.1
On Tue, 15 Jul 2003, Static wrote: > Just installed 5.1 yesterday, cvsuped using the . tag, and src-all > /etc/make.conf untouched. I attempted to buildworld and I get the following > > ranlib libc_pic.a > ranlib libc.a > ranlib libc_p.a > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc.a > /usr/obj/usr/sr > c/i386/usr/lib > sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libc_p.a > /usr/obj/usr/ > src/i386/usr/lib > sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libc.so.5 > /usr/obj/u > sr/src/i386/usr/lib > ln -fs libc.so.5 /usr/obj/usr/src/i386/usr/lib/libc.so > sh /usr/src/tools/install.sh -o root -g wheel -m 444 libc_pic.a > /usr/obj/usr/s > rc/i386/usr/lib > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > Did not see an open pr or anything mentioned in mailing lists. Is this a > known issue and should I file a pr, or is there a hack/workaround to fix > this? > > Thanks > > rwz Static, My buildworlds have been failing ever since the gcc 3.3 upgrade. I got the message that you got on one of the failures. However, my last three builds have consistently failed at the following point: ===> usr.sbin/keyserv cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/keyserv.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/setkey.c gzip -cn /usr/src/usr.sbin/keyserv/keyserv.8 > keyserv.8.gz cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c crypt_svc.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -c /usr/src/usr.sbin/keyserv/crypt_server.c cc -O -pipe -mcpu=pentiumpro -DKEYSERV_RANDOM -DBROKEN_DES -I. -o keyserv keyserv.o setkey.o crypt_svc.o crypt_server.o -lmp -lcrypto -lrpcsvc 1 error *** Error code 2 1 error *** Error code 2 1 error My make.conf is as follows: CFLAGS= -O -pipe NOPROFILE= true COPTFLAGS= -O -pipe COMPAT3X= yes COMPAT4X= yes BOOTWAIT= 0 USA_RESIDENT= YES DOC_LANG= en_US.ISO8859-1 PERL_VER= 5.8.0 PERL_VERSION= 5.8.0 PERL_ARCH= mach NOPERL= yo NO_PERL=yo NO_PERL_WRAPPER=yo My 5.x test machine is an Athlon 750 with 256 MB of RAM, and 1 GB of swap. I am using a clean /usr/obj directory for each build. I am using -j 6 for the buildworld. Maybe that is the problems, I will try taking that out. Anyway, I have not seen any mention on the lists of similar failures either. There must be something funky that we are doing. - Matt -- Matt Loschert - Software Engineer | email: [EMAIL PROTECTED]| ServInt Internet Services | web: http://www.servint.net/ | McLean, Virginia USA| phone: (703) 847-1381 | ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "[EMAIL PROTECTED]"
