Re: sparc64 tinderbox failure
Mike Barcroft [EMAIL PROTECTED] writes: Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html Sat Apr 5 03:38:00 EST 2003 U Makefile.inc1 cvs update: ignoring bin/dumplfs (CVS/Repository missing) cvs update: ignoring contrib/amd/conf/mount (CVS/Repository missing) cvs [update aborted]: cannot open CVS/Root: No such file or directory Bah. Sorry about the spam, my NFS server lost power. Best regards, Mike Barcroft ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
Peter Wemm [EMAIL PROTECTED] writes: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. nice try, but check rev 1.179 of src/share/man/man9/Makefile. 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: sparc64 tinderbox failure
Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
On Sat, Mar 29, 2003 at 11:02:53AM -0800, Peter Wemm wrote: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. Interesting. I saw the same thing here with last night's CVS. FreeBSD lizzy.catnook.com 5.0-CURRENT FreeBSD 5.0-CURRENT #102: Sat Mar 22 12:48:22 PST 2003 [EMAIL PROTECTED]:/disk0/usr/obj/disk0/usr/src/sys/LIZZY i386 -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ jos at catnook.com_/_/ _/_/_/ require 'std/disclaimer' ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
In message [EMAIL PROTECTED], Jos Backus writes: On Sat, Mar 29, 2003 at 11:02:53AM -0800, Peter Wemm wrote: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. Interesting. I saw the same thing here with last night's CVS. AOL twice. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
On Sat, Mar 29, 2003 at 08:18:48PM +0100, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Jos Backus writes: On Sat, Mar 29, 2003 at 11:02:53AM -0800, Peter Wemm wrote: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. Interesting. I saw the same thing here with last night's CVS. AOL twice. It was a single-bit error in imp's brain or fingers :) I fixed it last night. Kris pgp0.pgp Description: PGP signature ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
Jos Backus wrote: On Sat, Mar 29, 2003 at 11:02:53AM -0800, Peter Wemm wrote: Mike Barcroft wrote: stage 4: building everything.. -- === share/man/man9 make: don't know how to make bus_Activate_resource.9. Stop *** Error code 2 This looks like a single bit memory error to me. Turn off bit 5 and a lowercase a turns into an uppercase A. Interesting. I saw the same thing here with last night's CVS. Peter didn't say whether it was a SPARC64 single bit memory error, or a single bit memory error in the human who wrote the Makefile. ;^). -- Terry ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sparc64 tinderbox failure
On Mon, Mar 03, 2003 at 12:16:39AM -0500, Mike Barcroft wrote: [...] -- Kernel build for GENERIC started on Mon Mar 3 00:15:48 EST 2003 -- === hme make: don't know how to make bsd.README. Stop *** Error code 2 Should be fixed now. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
I made the suggestion in another forum that we create subscription lists for these tinderbox messages so that those interested could see them, and those not interested would not need to filter them out. Is anyone else interested in doing it that way? Or is this a solution looking for a problem? Doug -- This .signature sanitized for your protection To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Thus spake Doug Barton [EMAIL PROTECTED]: I made the suggestion in another forum that we create subscription lists for these tinderbox messages so that those interested could see them, and those not interested would not need to filter them out. Is anyone else interested in doing it that way? Or is this a solution looking for a problem? I think most people who track -CURRENT are subscribed to current@ precisely because they want to know when things break. Similarly for -STABLE, but that's a moot point because -STABLE doesn't break very often. For people who don't agree with this, there's always procmail; the reports aren't all that frequent that filtering is some sort of burden. I do, however, like the idea of consolidating them and providing more concise summaries. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
David Schultz wrote: Thus spake Doug Barton [EMAIL PROTECTED]: I made the suggestion in another forum that we create subscription lists for these tinderbox messages so that those interested could see them, and those not interested would not need to filter them out. Is anyone else interested in doing it that way? Or is this a solution looking for a problem? I think most people who track -CURRENT are subscribed to current@ precisely because they want to know when things break. Similarly for -STABLE, but that's a moot point because -STABLE doesn't break very often. For people who don't agree with this, there's always procmail; the reports aren't all that frequent that filtering is some sort of burden. I do, however, like the idea of consolidating them and providing more concise summaries. I agree. Even sometimes I hate got tinderbox message, in most cases I'm very interested. Jens To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Wed, Jan 08, 2003 at 11:25:12PM +, Mike Barcroft said words to the effect of; Tinderbox FAQ: http://people.FreeBSD.org/~mike/tinderbox.html -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- Kernel build for GENERIC started on Wed Jan 8 22:16:49 GMT 2003 -- === vx touch: /tinderbox/sparc64/obj/tinderbox/sparc64/src/sys/GENERIC/modules/tinderbox/sparc64/src/sys/modules/vx/export_syms: No such file or directory *** Error code 1 FWIW, I can't reproduce this locally, it must be a problem with the tinderbox. I haven't seen Mike around lately, hopefully he can see what's going on soon. Sorry for the spam. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Jake Burkholder [EMAIL PROTECTED] writes: Apparently, On Wed, Jan 08, 2003 at 11:25:12PM +, Mike Barcroft said words to the effect of; -- Kernel build for GENERIC started on Wed Jan 8 22:16:49 GMT 2003 -- === vx touch: /tinderbox/sparc64/obj/tinderbox/sparc64/src/sys/GENERIC/modules/tinderbox/sparc64/src/sys/modules/vx/export_syms: No such file or directory *** Error code 1 FWIW, I can't reproduce this locally, it must be a problem with the tinderbox. I haven't seen Mike around lately, hopefully he can see what's going on soon. Sorry for the spam. Hmm, I'll try clearing the obj directory and see if that helps. I did have some trouble with the filesystem the tinderbox runs on. fsck may have deleted some files that left things in an unexpected state. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Mon, Dec 30, 2002 at 03:21:22AM +, Mike Barcroft wrote: === sbin/swapon cc1: warnings being treated as errors /tinderbox/sparc64/src/sbin/swapon/swapon.c: In function `swaplist': /tinderbox/sparc64/src/sbin/swapon/swapon.c:246: warning: field width is not type int (arg 3) Can someone please just fix this (by backing out the offending commit, if necessary)? Kris msg49420/pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
Thus spake Kris Kennaway [EMAIL PROTECTED]: On Mon, Dec 30, 2002 at 03:21:22AM +, Mike Barcroft wrote: === sbin/swapon cc1: warnings being treated as errors /tinderbox/sparc64/src/sbin/swapon/swapon.c: In function `swaplist': /tinderbox/sparc64/src/sbin/swapon/swapon.c:246: warning: field width is not type int (arg 3) Can someone please just fix this (by backing out the offending commit, if necessary)? Eek, given a 64-bit size_t, the present code leaves 32 bits of it uninitialized in the usual case. The following patch ought to fix the problem; I can't make sure right now because I'm out of town. Index: swapon.c === RCS file: /home/ncvs/src/sbin/swapon/swapon.c,v retrieving revision 1.14 diff -u -r1.14 swapon.c --- swapon.c2002/12/28 23:39:47 1.14 +++ swapon.c2002/12/30 05:15:54 @@ -211,7 +211,7 @@ size_t mibsize, size; struct xswdev xsw; int mib[16], n, pagesize; - size_t hlen; + int hlen; long blocksize; long long total = 0; long long used = 0; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Sun, Dec 29, 2002 at 09:17:05PM -0800, David Schultz wrote:
Thus spake Kris Kennaway [EMAIL PROTECTED]:
On Mon, Dec 30, 2002 at 03:21:22AM +, Mike Barcroft wrote:
=== sbin/swapon
cc1: warnings being treated as errors
/tinderbox/sparc64/src/sbin/swapon/swapon.c: In function `swaplist':
/tinderbox/sparc64/src/sbin/swapon/swapon.c:246: warning: field width is not
type int (arg 3)
Can someone please just fix this (by backing out the offending commit,
if necessary)?
Eek, given a 64-bit size_t, the present code leaves 32 bits of it
uninitialized in the usual case. The following patch ought to fix
the problem; I can't make sure right now because I'm out of town.
I'm not sure if your patch will solve the problem.
The offending code is here:
240 if (lflag) {
241 char buf[32];
242 snprintf(buf, sizeof(buf), %ld-blocks, blocksize);
243 printf(%-13s %*s %*s\n,
244 Device:,
245 hlen, buf,
246 hlen, Used:);
247 }
Doesn't the printf() statement in question have the wrong number of
arguments?
--
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
* De: Craig Rodrigues [EMAIL PROTECTED] [ Data: 2002-12-29 ]
[ Subjecte: Re: sparc64 tinderbox failure ]
I'm not sure if your patch will solve the problem.
The offending code is here:
240 if (lflag) {
241 char buf[32];
242 snprintf(buf, sizeof(buf), %ld-blocks, blocksize);
243 printf(%-13s %*s %*s\n,
244 Device:,
245 hlen, buf,
246 hlen, Used:);
247 }
Doesn't the printf() statement in question have the wrong number of
arguments?
No, it's using variable field-length specifiers.
--
Juli Mallett [EMAIL PROTECTED]
AIM: BSDFlata IRC: juli@EFnet#flata
OpenDarwin, Mono, FreeBSD Developer.
ircd-hybrid Developer, EFnet addict.
FreeBSD on MIPS-Anything on FreeBSD.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Thus spake Juli Mallett [EMAIL PROTECTED]:
* De: Craig Rodrigues [EMAIL PROTECTED] [ Data: 2002-12-29 ]
[ Subjecte: Re: sparc64 tinderbox failure ]
I'm not sure if your patch will solve the problem.
The offending code is here:
240 if (lflag) {
241 char buf[32];
242 snprintf(buf, sizeof(buf), %ld-blocks, blocksize);
243 printf(%-13s %*s %*s\n,
244 Device:,
245 hlen, buf,
246 hlen, Used:);
247 }
Doesn't the printf() statement in question have the wrong number of
arguments?
No, it's using variable field-length specifiers.
Right. The complaint is that hlen is 64 bits and the printf()
expects the field length specifier to be an int. The same goes
for getbsize(hlen, ...), so I'm not sure why the compiler didn't
complain about a type mismatch. I guess it just coerced the
pointer to an int *.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Thus spake David Schultz [EMAIL PROTECTED]: Right. The complaint is that hlen is 64 bits and the printf() expects the field length specifier to be an int. The same goes for getbsize(hlen, ...), so I'm not sure why the compiler didn't complain about a type mismatch. I guess it just coerced the pointer to an int *. Aah, the compiler didn't complain because the getbsize() interface was changed between -CURRENT and -STABLE, and it now takes a 'size_t *' instead of an 'int *' to fill in with the length of the string. (To me, this change seems absolutely ridiculous, because the number in question is seldom greater than 10, much less 2^64.) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Fri, Dec 20, 2002 at 03:26:36AM +, Mike Barcroft said words to the effect of; -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /tinderbox/sparc64/obj/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- stage 4: make dependencies -- stage 4: building everything.. -- === sys/boot/sparc64/loader In file included from /tinderbox/sparc64/src/sys/boot/sparc64/loader/locore.S:15: machine/asm.h:105:1: warning: __FBSDID redefined In file included from machine/asm.h:46, from /tinderbox/sparc64/src/sys/boot/sparc64/loader/locore.S:15: /tinderbox/sparc64/src/sys/sys/cdefs.h:239:1: warning: this is the location of the previous definition /tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:110: `zipfs_fsops' undeclared here (not in a function) /tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:110: initializer element is not constant /tinderbox/sparc64/src/sys/boot/sparc64/loader/main.c:110: (near initialization for `file_system[2]') *** Error code 1 Fixed, my apologies. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Mon, Dec 02, 2002 at 04:17:34PM -0500, John Baldwin wrote: On 29-Nov-2002 Mike Barcroft wrote: Ruslan Ermilov [EMAIL PROTECTED] writes: On Fri, Nov 29, 2002 at 03:22:29AM +, Mike Barcroft wrote: Fri Nov 29 03:15:00 GMT 2002 U lib/libpam/modules/pam_ksu/pam_ksu.c U release/doc/en_US.ISO8859-1/early-adopter/article.sgml Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Are you using NFS here? Only the CVS repo is NFS mounted. And you don't have INSTALL= install -C, correct? Yes, he was building under non-root. This problem is already resolved. Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg48022/pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
On 29-Nov-2002 Mike Barcroft wrote: Ruslan Ermilov [EMAIL PROTECTED] writes: On Fri, Nov 29, 2002 at 03:22:29AM +, Mike Barcroft wrote: Fri Nov 29 03:15:00 GMT 2002 U lib/libpam/modules/pam_ksu/pam_ksu.c U release/doc/en_US.ISO8859-1/early-adopter/article.sgml Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Are you using NFS here? Only the CVS repo is NFS mounted. And you don't have INSTALL= install -C, correct? -- John Baldwin [EMAIL PROTECTED]http://www.FreeBSD.org/~jhb/ Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Fri, Nov 29, 2002 at 03:22:29AM +, Mike Barcroft wrote: Fri Nov 29 03:15:00 GMT 2002 U lib/libpam/modules/pam_ksu/pam_ksu.c U release/doc/en_US.ISO8859-1/early-adopter/article.sgml Running test variables PASS: Test variables detected no regression, output matches. Running test targets PASS: Test targets detected no regression. Running test sysvmatch PASS: Test sysvmatch detected no regression. Running test lhs_expn PASS: Test lhs_expn detected no regression. Running test notdef PASS: Test notdef detected no regression. Running test modifiers PASS: Test modifiers detected no regression. Running test funny_targets FAIL: Test failed: regression detected. See above. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. *** Error code 1 Stop in /tinderbox/sparc64/src/tools/regression/usr.bin/make. -- Upgrading the installed make -- install: /usr/bin/make: Text file busy *** Error code 71 Are you using NFS here? Cheers, -- Ruslan Ermilov Sysadmin and DBA, [EMAIL PROTECTED] Sunbay Software AG, [EMAIL PROTECTED] FreeBSD committer, +380.652.512.251Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age msg47732/pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
On Thu, Nov 21, 2002 at 09:20:41AM +, Mike Barcroft wrote: Thu Nov 21 09:15:00 GMT 2002 ... U sys/kern/kern_thread.c U sys/kern/sched_4bsd.c U sys/modules/netgraph/bluetooth/bluetooth/Makefile U sys/modules/netgraph/bluetooth/bt3c/Makefile U sys/modules/netgraph/bluetooth/h4/Makefile U sys/modules/netgraph/bluetooth/hci/Makefile U sys/modules/netgraph/bluetooth/l2cap/Makefile U sys/modules/netgraph/bluetooth/socket/Makefile U sys/modules/netgraph/bluetooth/ubt/Makefile cvs [update aborted]: cannot make directory include: File exists Looks like this (and the alpha tinderbox) needs manual intervention following the bluetooth re-import (there was repo surgery after the first failed import). Kris msg47122/pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
On Sun, 17 Nov 2002, Mike Barcroft wrote: -- Kernel build for GENERIC started on Sun Nov 17 20:01:33 GMT 2002 -- === ipfilter /tinderbox/sparc64/src/sys/kern/kern_thread.c: In function `kse_create': /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: `mp_ncpus' undeclared (first use in this function) /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: (Each undeclared identifier is reported only once /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: for each function it appears in.) ok mea culpa.. what is there in SPARC that should be used instead..? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Sun, Nov 17, 2002 at 12:23:20PM -0800, Julian Elischer said words to the effect of; On Sun, 17 Nov 2002, Mike Barcroft wrote: -- Kernel build for GENERIC started on Sun Nov 17 20:01:33 GMT 2002 -- === ipfilter /tinderbox/sparc64/src/sys/kern/kern_thread.c: In function `kse_create': /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: `mp_ncpus' undeclared (first use in this function) /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: (Each undeclared identifier is reported only once /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: for each function it appears in.) ok mea culpa.. what is there in SPARC that should be used instead..? mp_ncpus is defined in sys/smp.h which is not included kern_thread.c I don't see why this builds on any platform. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Sun, Nov 17, 2002 at 03:46:55PM -0500, Jake Burkholder wrote: Apparently, On Sun, Nov 17, 2002 at 12:23:20PM -0800, Julian Elischer said words to the effect of; On Sun, 17 Nov 2002, Mike Barcroft wrote: -- Kernel build for GENERIC started on Sun Nov 17 20:01:33 GMT 2002 -- === ipfilter /tinderbox/sparc64/src/sys/kern/kern_thread.c: In function `kse_create': /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: `mp_ncpus' undeclared (first use in this function) /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: (Each undeclared identifier is reported only once /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: for each function it appears in.) ok mea culpa.. what is there in SPARC that should be used instead..? mp_ncpus is defined in sys/smp.h which is not included kern_thread.c I don't see why this builds on any platform. Jake This does not compile on i386 with options SMP, either. It looks like a '#if 0' was removed in kern_thread.c rev 1.61, which exposes bug in SMP case. Something like this should fix kernel building. (I have no idea where to place the #include, though) Index: kern_thread.c === RCS file: /home/ncvs/src/sys/kern/kern_thread.c,v retrieving revision 1.61 diff -u -r1.61 kern_thread.c --- kern_thread.c 17 Nov 2002 11:47:03 - 1.61 +++ kern_thread.c 17 Nov 2002 22:22:35 - @@ -47,6 +47,10 @@ #include sys/ktr.h #include sys/ucontext.h +#ifdef SMP +#include sys/smp.h +#endif + #include vm/vm.h #include vm/vm_object.h #include vm/pmap.h To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Sun, 17 Nov 2002, Jake Burkholder wrote: Apparently, On Sun, Nov 17, 2002 at 12:23:20PM -0800, Julian Elischer said words to the effect of; On Sun, 17 Nov 2002, Mike Barcroft wrote: -- Kernel build for GENERIC started on Sun Nov 17 20:01:33 GMT 2002 -- === ipfilter /tinderbox/sparc64/src/sys/kern/kern_thread.c: In function `kse_create': /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: `mp_ncpus' undeclared (first use in this function) /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: (Each undeclared identifier is reported only once /tinderbox/sparc64/src/sys/kern/kern_thread.c:498: for each function it appears in.) ok mea culpa.. what is there in SPARC that should be used instead..? mp_ncpus is defined in sys/smp.h which is not included kern_thread.c I don't see why this builds on any platform. #if 0 /* while debugging */ #ifdef SMP if (kg-kg_kses mp_ncpus) #endif return (EPROCLIM); #endif (last night) seems to have changed in the last 12 hours to: #ifdef SMP if (kg-kg_kses mp_ncpus) #endif return (EPROCLIM); i.e. the #if 0 seems to have disappeared... I guess that David Xu forgot to include smp.h in his patch. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Mike Barcroft wrote: -- Kernel build for GENERIC started on Fri Nov 15 14:04:21 GMT 2002 -- === ipfilter cc1: warnings being treated as errors /tinderbox/sparc64/src/sys/dev/gem/if_gem.c: In function `gem_start': /tinderbox/sparc64/src/sys/dev/gem/if_gem.c:1232: warning: passing arg 1 of `bpf_mtap' from incompatible pointer type /tinderbox/sparc64/src/sys/dev/gem/if_gem.c: In function `gem_rint': /tinderbox/sparc64/src/sys/dev/gem/if_gem.c:1457: warning: unused variable `eh' *** Error code 1 I believe my last commit to if_gem.c fixed this. Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote: You can also get various new machines on sun.com for around $1000 USD, IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours. A $1000 (new) 500 MHz blade running GENERIC (minus WITNESS) builds world in a little under 3 hours. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
David O'Brien writes: On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote: You can also get various new machines on sun.com for around $1000 USD, IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours. A $1000 (new) 500 MHz blade running GENERIC (minus WITNESS) builds world in a little under 3 hours. Or just a little slower than my 4 year old 500MHz 21264 ($1000 used) alpha. Darn. I was hoping a reasonbly priced sparc64 would be fast enough that getting one would allow me to find LP64 problems quicker due to a faster buildworld cycle. It's really frustrating to get 2+ hours into a buildworld and have it die because of a problem in usr.sbin I guess we'll need to wait for x86-64 for that. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Tue, Oct 29, 2002 at 08:55:03AM -0500, Andrew Gallatin said words to the effect of; David O'Brien writes: On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote: You can also get various new machines on sun.com for around $1000 USD, IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours. A $1000 (new) 500 MHz blade running GENERIC (minus WITNESS) builds world in a little under 3 hours. Or just a little slower than my 4 year old 500MHz 21264 ($1000 used) alpha. Darn. I was hoping a reasonbly priced sparc64 would be fast enough that getting one would allow me to find LP64 problems quicker due to a faster buildworld cycle. It's really frustrating to get 2+ hours into a buildworld and have it die because of a problem in usr.sbin I guess we'll need to wait for x86-64 for that. Cross build on a fast x86 box... My 1.2ghz athlon running -stable builds a sparc64 world in about half an hour. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Thu, 24 Oct 2002, Andrew Gallatin wrote: Mike Barcroft writes: stage 4: building everything.. -- === usr.sbin/pkg_install/info cc1: warnings being treated as errors /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c: In function `show_size': /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c:239: warning: passing arg 1 of `getbsize' from incompatible pointer type *** Error code 1 I fixed this an hour or 2 ago when I hit it on my alpha. How long does a sparc64 buildworld take on reasonably priced hardware? Where resonable means = $1000 USD, used OK. I pointed out this breakage a day or two ago. The breakage has since been expanded by breaking most of the messengers, but but pkg_install until you hit it. The complete list of messages in usr/src is easy to find using grep. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Mike Barcroft writes: stage 4: building everything.. -- === usr.sbin/pkg_install/info cc1: warnings being treated as errors /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c: In function `show_size': /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c:239: warning: passing arg 1 of `getbsize' from incompatible pointer type *** Error code 1 I fixed this an hour or 2 ago when I hit it on my alpha. How long does a sparc64 buildworld take on reasonably priced hardware? Where resonable means = $1000 USD, used OK. Drew Gallatin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Thu, Oct 24, 2002 at 04:19:09PM -0400, Andrew Gallatin said words to the effect of; Mike Barcroft writes: stage 4: building everything.. -- === usr.sbin/pkg_install/info cc1: warnings being treated as errors /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c: In function `show_size': /tinderbox/sparc64/src/usr.sbin/pkg_install/info/show.c:239: warning: passing arg 1 of `getbsize' from incompatible pointer type *** Error code 1 I fixed this an hour or 2 ago when I hit it on my alpha. How long does a sparc64 buildworld take on reasonably priced hardware? Where resonable means = $1000 USD, used OK. You can get a dual 300mhz ultra 60 on ebay for $900-1000 USD. Mine does a make -j 8 buildworld in just over 2 hours with some strategic stuff turned off in make.conf (profiled libs, objective c, fortran). Thu Oct 24 15:10:18 GMT 2002 7546.53 real 10633.14 user 1818.80 sys Search for sun ultra on ebay; I got mine from paladintech. Ultra 10s are cheaper but more PC class, my 300mhz does a full buildworld in about 5 hours last time I timed it. Ultra 2 is probably the best value, but we don't support the builtin scsi controller yet. You can also get various new machines on sun.com for around $1000 USD, IIRC a 500mhz blade 100 does a buildworld in around 2-3 hours. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Thu, Oct 24, 2002 at 06:39:15PM -0400, Jake Burkholder wrote: You can get a dual 300mhz ultra 60 on ebay for $900-1000 USD. Mine does a make -j 8 buildworld in just over 2 hours with some strategic stuff turned off in make.conf (profiled libs, objective c, fortran). I got my ultra 30 on ebay for $250..it's just (still) missing a disk. You can find good bargains if you're willing to be patient and hunt for them. My NFS-backed buildworld times probably aren't relevant here :-) Kris msg45160/pgp0.pgp Description: PGP signature
Re: sparc64 tinderbox failure
In message [EMAIL PROTECTED], Mike Barcroft writes: === lib/libdisk cc1: warnings being treated as errors /tinderbox/sparc64/src/lib/libdisk/disk.c:428: warning: `assignToPartition' defined but not used I'm actively working on this stuff, but will be at customer sites today so if this gets in your way just disconnect libdisk from the build. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Fri, Oct 11, 2002 at 01:25:29PM +, Mike Barcroft wrote: -- === gnu/usr.bin/binutils/libbfd In file included from /tinderbox/sparc64/src/contrib/binutils/bfd/elf32.c:22: ... /tinderbox/sparc64/src/contrib/binutils/bfd/elflink.h:8389: structure has no member named `locsym_shndx' *** Error code 1 ?? -- elf make world completed on Fri Oct 11 03:56:01 PDT 2002 (started Fri Oct 11 00:47:38 PDT 2002) -- blade100# To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Mon, 2 Sep 2002 19:51:59 GMT Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: === gnu/usr.bin/cc/cc1plus method.o: In function `use_thunk': method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk' Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself? Buildworld completes fine on panther, the only FreeBSD sparc64 machine I have access to. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Alexander Kabaev [EMAIL PROTECTED] writes: On Mon, 2 Sep 2002 19:51:59 GMT Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: === gnu/usr.bin/cc/cc1plus method.o: In function `use_thunk': method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk' Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself? Buildworld completes fine on panther, the only FreeBSD sparc64 machine I have access to. The complete transcript is available here: http://sparc64.style9.org/sparc64.log Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
The complete transcript is available here: http://sparc64.style9.org/sparc64.log Which still does not answer my question. What GCC version is on this machine? -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Alexander Kabaev [EMAIL PROTECTED] writes: The complete transcript is available here: http://sparc64.style9.org/sparc64.log Which still does not answer my question. What GCC version is on this machine? Sorry, I thought your question was whether it was in the cross building stage or later on in the build. %gcc -v Using built-in specs. Configured with: FreeBSD/sparc64 system compiler Thread model: posix gcc version 3.1 [FreeBSD] 20020509 (prerelease) I can provide you with an account on the system. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Alexander Kabaev wrote: On Mon, 2 Sep 2002 19:51:59 GMT Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: === gnu/usr.bin/cc/cc1plus method.o: In function `use_thunk': method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk' Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself? Buildworld completes fine on panther, the only FreeBSD sparc64 machine I have access to. This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c is out of sync on the builder machine. This builds fine on panther.freebsd.org. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Apparently, On Mon, Sep 02, 2002 at 08:21:12PM -0700, Peter Wemm said words to the effect of; Alexander Kabaev wrote: On Mon, 2 Sep 2002 19:51:59 GMT Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: === gnu/usr.bin/cc/cc1plus method.o: In function `use_thunk': method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk' Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself? Buildworld completes fine on panther, the only FreeBSD sparc64 machine I have access to. This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c is out of sync on the builder machine. This builds fine on panther.freebsd.org. Yeah, I just finished a native world here and have cross built several since the compiler upgrade. Jake To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Peter Wemm [EMAIL PROTECTED] writes: Alexander Kabaev wrote: On Mon, 2 Sep 2002 19:51:59 GMT Dag-Erling Smorgrav [EMAIL PROTECTED] wrote: === gnu/usr.bin/cc/cc1plus method.o: In function `use_thunk': method.o(.text+0x90c): undefined reference to `sparc_output_mi_thunk' Is this gcc 3.1 trying to build 3.2 or gcc 3.2 trying to build itself? Buildworld completes fine on panther, the only FreeBSD sparc64 machine I have access to. This has got to be a local problem, perhaps where src/contrib/sparc/sparc.c is out of sync on the builder machine. This builds fine on panther.freebsd.org. The source directory had some stale copies of files that weren't being updated. I fixed them, so hopefully the next build will work correctly. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav wrote: -- stage 4: building everything.. -- === sbin/fsck_ffs cc1: warnings being treated as errors /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c: In function `bread': /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c:365: warning: long long int format, long int arg (arg 2) /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c:365: warning: long long int format, long int arg (arg 3) /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c:367: warning: long long int format, long int arg (arg 2) /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c: In function `bwrite': /usr/home/des/tinderbox/sparc64/src/sbin/fsck_ffs/fsutil.c:402: warning: long long int format, long int arg (arg 2) *** Error code 1 This should be fixed now. Maxime To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Mike Barcroft [EMAIL PROTECTED] writes: Thanks. Do you want to increase the tinderbox to run twice a day? Sure, done. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree -- stage 2: rebuilding the object tree -- stage 2: build tools -- stage 3: cross tools -- stage 4: populating /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include -- stage 4: building libraries -- === lib/libc ... /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:88: structure has no member named `highpc' /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:88: structure has no member named `lowpc' /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:116: structure has no member named `highpc' /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:116: structure has no member named `lowpc' /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c: In function `_mcleanup': [...] DES, there wasn't enough context on this to solve the problem. Maybe the URL to the complete log should be appended to the message. I just committed a fix for this problem. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Mike Barcroft [EMAIL PROTECTED] writes: DES, there wasn't enough context on this to solve the problem. I don't really see what more you need. What's missing? The first line and cause of the subsequent errors: In file included from /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:43: /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include/sys/gmon.h:168: syntax error before uintfptr_t Since when I see: /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:86: structure has no member named `lowpc' /usr/home/des/tinderbox/sparc64/src/lib/libc/gmon/gmon.c:87: structure has no member named `highpc' ...it doesn't immediately occur to me that the reason those members don't exist is because of a syntax error. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Mike Barcroft [EMAIL PROTECTED] writes: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Mike Barcroft [EMAIL PROTECTED] writes: DES, there wasn't enough context on this to solve the problem. I don't really see what more you need. What's missing? The first line and cause of the subsequent errors: Ah, looks like a bug in whereintheworld. It's not supposed to truncate error messages. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Ah, looks like a bug in whereintheworld. It's not supposed to truncate error messages. I've hacked whereintheworld to print everything since the last '===' in case of an error, rather than just the last ten lines. If anyone is interested it's in ~des/bin on freefall. I've already updated the copy on bowie, so the sparc64 builds should be fine now. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Ah, looks like a bug in whereintheworld. It's not supposed to truncate error messages. I've hacked whereintheworld to print everything since the last '===' in case of an error, rather than just the last ten lines. If anyone is interested it's in ~des/bin on freefall. I've already updated the copy on bowie, so the sparc64 builds should be fine now. Thanks. Do you want to increase the tinderbox to run twice a day? Not many people are using the system since a sparc64 was added to the cluster. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- Kernel build for GENERIC started on Sat Jul 27 11:45:42 GMT 2002 -- === GENERIC /usr/home/des/tinderbox/sparc64/src/sys/sparc64/conf/GENERIC: unknown option PCI_ENABLE_IO_MODES *** Error code 1 I just committed a fix for this. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- stage 4: building everything.. -- === usr.sbin/mrouted/testrsrr === usr.sbin/mtest === usr.sbin/mtree === usr.sbin/ndp === usr.sbin/newsyslog === usr.sbin/nfsd /usr/home/des/tinderbox/sparc64/src/usr.sbin/nfsd/nfsd.c: In function `start_server': /usr/home/des/tinderbox/sparc64/src/usr.sbin/nfsd/nfsd.c:836: invalid use of undefined type `struct nfsd_srvargs' /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sparc64/usr/include/stdio.h: At top level: /usr/home/des/tinderbox/sparc64/src/usr.sbin/nfsd/nfsd.c:84: storage size of `nsd' isn't known *** Error code 1 Looks like Peter fixed this in rev 1.28. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
John Polstra [EMAIL PROTECTED] writes:
Does tinderbox run with a nonstandard WARNS setting? I did the
cross build with these environment settings:
des@freefall ~% cat tinderbox/make.conf
CFLAGS = -O -pipe
COPTFLAGS= -O -pipe
NOPROFILE= true
MAKE_KERBEROS4 = yes
MAKE_KERBEROS5 = yes
and the relevant bits of tinderbox.sh:
/bin/mkdir -p ${obj}
MAKEOBJDIRPREFIX=${obj}; export MAKEOBJDIRPREFIX
__MAKE_CONF=${base}/make.conf; export __MAKE_CONF
/usr/bin/make -s buildworld
for kc in ${kernels} ; do
(cd sys/${arch}/conf make ${kc})
/usr/bin/make -s buildkernel KERNCONF=${kc} -DNO_WERROR
done
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
In article [EMAIL PROTECTED],
Dag-Erling Smorgrav [EMAIL PROTECTED] wrote:
John Polstra [EMAIL PROTECTED] writes:
Does tinderbox run with a nonstandard WARNS setting? I did the
cross build with these environment settings:
des@freefall ~% cat tinderbox/make.conf
CFLAGS = -O -pipe
COPTFLAGS= -O -pipe
NOPROFILE= true
MAKE_KERBEROS4 = yes
MAKE_KERBEROS5 = yes
and the relevant bits of tinderbox.sh:
/bin/mkdir -p ${obj}
MAKEOBJDIRPREFIX=${obj}; export MAKEOBJDIRPREFIX
__MAKE_CONF=${base}/make.conf; export __MAKE_CONF
/usr/bin/make -s buildworld
for kc in ${kernels} ; do
(cd sys/${arch}/conf make ${kc})
/usr/bin/make -s buildkernel KERNCONF=${kc} -DNO_WERROR
done
Now I'm really confused. If the script is passing -DNO_WERROR to
the buildkernel invocation then why did a warning kill the build?
John
--
John Polstra
John D. Polstra Co., Inc.Seattle, Washington USA
Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- Kernel build for GENERIC started on Wed Jul 24 11:45:59 GMT 2002 -- === GENERIC FYI: static unit limits for ppp are set: NPPP=1 Kernel build directory is /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sys/GENERIC Don't forget to do a ``make depend'' ./aicasm: 873 instructions used cc1: warnings being treated as errors /usr/home/des/tinderbox/sparc64/src/sys/kern/uipc_socket.c: In function `soreceive': /usr/home/des/tinderbox/sparc64/src/sys/kern/uipc_socket.c:841: warning: long unsigned int format, different type arg (arg 3) *** Error code 1 I just committed a fix for this. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
In article [EMAIL PROTECTED], Mike Barcroft [EMAIL PROTECTED] wrote: Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- Kernel build for GENERIC started on Wed Jul 24 11:45:59 GMT 2002 -- === GENERIC FYI: static unit limits for ppp are set: NPPP=1 Kernel build directory is /home/des/tinderbox/sparc64/obj/usr/home/des/tinderbox/sparc64/src/sys/GENERIC Don't forget to do a ``make depend'' ./aicasm: 873 instructions used cc1: warnings being treated as errors /usr/home/des/tinderbox/sparc64/src/sys/kern/uipc_socket.c: In function `soreceive': /usr/home/des/tinderbox/sparc64/src/sys/kern/uipc_socket.c:841: warning: long unsigned int format, different type arg (arg 3) *** Error code 1 I just committed a fix for this. Thanks, Mike! Sorry, folks! I tested with an i386-alpha cross build including (I'm almost certain) a buildkernel. I'm not sure why it didn't catch this. Does tinderbox run with a nonstandard WARNS setting? I did the cross build with these environment settings: TARGET_ARCH=alpha __MAKE_CONF=/dev/null John -- John Polstra John D. Polstra Co., Inc.Seattle, Washington USA Disappointment is a good sign of basic intelligence. -- Chögyam Trungpa To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Wed, 2002-07-17 at 05:54, Dag-Erling Smorgrav wrote: === sbin/newfs /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c: In function `fsinit': /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c:711: structure has no member named `di_createtime' *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sbin/newfs. *** Error code 1 Same error on i386 build. -- Remember: the only difference between being the champ and the chump is u. signature.asc Description: This is a digitally signed message part
Re: sparc64 tinderbox failure
On (2002/07/17 06:49), Rob Hughes wrote: === sbin/newfs /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c: In function `fsinit': /usr/home/des/tinderbox/sparc64/src/sbin/newfs/mkfs.c:711: structure has no member named `di_createtime' *** Error code 1 Stop in /usr/home/des/tinderbox/sparc64/src/sbin/newfs. *** Error code 1 Same error on i386 build. Patches posted in Message-ID: [EMAIL PROTECTED], sent to cvs-committers and cvs-all. I haven't committed them myself, because I haven't tested whether the resulting newfs binary works. Ciao, Sheldon. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- stage 4: building everything.. -- === gnu/lib/libobjc === gnu/lib/libg2c === gnu/usr.bin === gnu/usr.bin/bc === gnu/usr.bin/binutils === gnu/usr.bin/binutils/libiberty === gnu/usr.bin/binutils/libbfd cc1: warnings being treated as errors /usr/home/des/tinderbox/sparc64/src/contrib/binutils/bfd/elf-eh-frame.c: In function `_bfd_elf_discard_section_eh_frame': /usr/home/des/tinderbox/sparc64/src/contrib/binutils/bfd/elf-eh-frame.c:417: warning: comparison between signed and unsigned *** Error code 1 I've reduced the WARNS level in the sparc64 case until David has a chance to look at my patch which fixes this warning. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Thu, 11 Jul 2002, Mike Barcroft wrote:
Giorgos Keramidas [EMAIL PROTECTED] writes:
Whoever fixes this, and however we agree to fix it,
should also remember to close the bin/40382 PR.
Comments on the attached, untested patch?
Disable fatal warnings during bootstrap, build, and cross tools
phase of world.
The setting of NO_WERROR belongs in [BTX]MAKE if anywhere. This is
already done for [BX]MAKE but not for TMAKE. However, I don't like
turning off warnings for any of these. Warnings for these stages may
be even more important and should be less likely than warnings for
building the final world, since it is very important for basic tools
to be correct and for their source to be careful about portabilty
issues.
Index: Makefile.inc1
===
RCS file: /work/repo/src/Makefile.inc1,v
retrieving revision 1.294
diff -u -r1.294 Makefile.inc1
--- Makefile.inc1 1 Jul 2002 17:51:43 - 1.294
+++ Makefile.inc1 11 Jul 2002 04:50:02 -
@@ -589,8 +589,8 @@
${_cxx_consumers} gnu/usr.bin/texinfo
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
- ${MAKE} DIRPRFX=${_tool}/ depend; \
- ${MAKE} DIRPRFX=${_tool}/ all; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true depend; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true all; \
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX} install
.endfor
...
This also has some style bugs :). Any setting of NO_WERROR turns it on,
so setting it to different spellings of boolean true is just confusing.
It is set correctly for for [BX]MAKE.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Bruce Evans [EMAIL PROTECTED] writes: On Thu, 11 Jul 2002, Mike Barcroft wrote: Comments on the attached, untested patch? Disable fatal warnings during bootstrap, build, and cross tools phase of world. The setting of NO_WERROR belongs in [BTX]MAKE if anywhere. This is already done for [BX]MAKE but not for TMAKE. However, I don't like turning off warnings for any of these. Warnings for these stages may be even more important and should be less likely than warnings for building the final world, since it is very important for basic tools to be correct and for their source to be careful about portabilty issues. Well, unfortunately I don't think we can depend on older compilers having correct warnings. In PR 40382, it would seem the 4.5 - HEAD upgrade path is broken because of fatal warnings. A good workaround for that problem might be specifying NO_WERROR for the entire build, in which case -Werror becomes useless anyway. So we might just as well disable early fatal warnings and hope that developers can catch most of the bugs later on in the build. This also has some style bugs :). Any setting of NO_WERROR turns it on, so setting it to different spellings of boolean true is just confusing. It is set correctly for for [BX]MAKE. Oh, that's a much nicer location. :) I think only BMAKE has NO_WERROR defined, not XMAKE. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On 2002-07-10 09:58 +, Dag-Erling Smorgrav wrote:
=== bin/chmod
cc1: warnings being treated as errors
/usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c: In function `main':
/usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c:174: warning: null format
string
How does this look for fixing this warning?
%%%
Index: chmod.c
===
RCS file: /home/ncvs/src/bin/chmod/chmod.c,v
retrieving revision 1.25
diff -u -r1.25 chmod.c
--- chmod.c 30 Jun 2002 05:13:52 - 1.25
+++ chmod.c 10 Jul 2002 17:22:22 -
@@ -171,7 +171,7 @@
}
if ((ftsp = fts_open(++argv, fts_options, 0)) == NULL)
- err(1, NULL);
+ err(1, %s: %s, *argv, strerror(p-fts_errno));
for (rval = 0; (p = fts_read(ftsp)) != NULL;) {
switch (p-fts_info) {
case FTS_D: /* Change it at FTS_DP. */
%%%
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Giorgos Keramidas [EMAIL PROTECTED] writes: How does this look for fixing this warning? No, gcc should accept a NULL format string for err(3). It looks like __printf0like is broken. DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Wed, 10 Jul 2002, Giorgos Keramidas wrote:
On 2002-07-10 09:58 +, Dag-Erling Smorgrav wrote:
=== bin/chmod
cc1: warnings being treated as errors
/usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c: In function `main':
/usr/home/des/tinderbox/sparc64/src/bin/chmod/chmod.c:174: warning: null format
string
How does this look for fixing this warning?
%%%
Index: chmod.c
===
RCS file: /home/ncvs/src/bin/chmod/chmod.c,v
retrieving revision 1.25
diff -u -r1.25 chmod.c
--- chmod.c 30 Jun 2002 05:13:52 - 1.25
+++ chmod.c 10 Jul 2002 17:22:22 -
@@ -171,7 +171,7 @@
}
if ((ftsp = fts_open(++argv, fts_options, 0)) == NULL)
- err(1, NULL);
+ err(1, %s: %s, *argv, strerror(p-fts_errno));
for (rval = 0; (p = fts_read(ftsp)) != NULL;) {
switch (p-fts_info) {
case FTS_D: /* Change it at FTS_DP. */
%%%
The main bug is that the warning is emitted. err(1, NULL) is perfectly
valid (see err(4)). Apparently the sparc64 compiler is missing support
for __printf0like.
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On 2002-07-10 14:22 +, Matthew Dillon wrote: :Giorgos Keramidas [EMAIL PROTECTED] writes: : How does this look for fixing this warning? : :No, gcc should accept a NULL format string for err(3). It looks like :__printf0like is broken. Oops. I've already starting changing the calls to err(). I would really like buildworld to work and there aren't too many of them, and besides a little more verboseness for some of these failures is not a bad thing. The extra verboseness is fine, and I was almost finished posting a note that mentioned it. But I didn't thinking that the __printf0like bugs will never be fixed if we hide them by patching chmod. Nevertheless, I do agree that a more verbose error message is likely to be an improvement in this particular case. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
: :Giorgos Keramidas [EMAIL PROTECTED] writes: : How does this look for fixing this warning? : :No, gcc should accept a NULL format string for err(3). It looks like :__printf0like is broken. : :DES :-- :Dag-Erling Smorgrav - [EMAIL PROTECTED] Oops. I've already starting changing the calls to err(). I would really like buildworld to work and there aren't too many of them, and besides a little more verboseness for some of these failures is not a bad thing. I'm going to finish what I've been doing and if someone has a real huge chip on their shoulder and can't handle the strain then they can fix __printf0like and then back-out some or all of my changes with my permission. Personally speaking, as much as GCC annoys me it is sometimes better to modify the utility code then to add yet another hack to GCC that needs to be synchronized every time we update. -Matt Matthew Dillon [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Bruce Evans [EMAIL PROTECTED] writes:
The main bug is that the warning is emitted. err(1, NULL) is perfectly
valid (see err(4)). Apparently the sparc64 compiler is missing support
for __printf0like.
Strangely, my Alpha (July 3 -CURRENT) complains about this too, but my
i386 (June 24 -CURRENT) doesn't. Here's my test program:
#include stdio.h
int
main(void)
{
printf(NULL);
return 0;
}
on Alpha, I get
des@dsa ~% gcc -Wformat -c /tmp/format.c
/tmp/format.c: In function `main':
/tmp/format.c:6: warning: null format string
on i386, I don't get a warning.
DES
--
Dag-Erling Smorgrav - [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Thu, 11 Jul 2002, Giorgos Keramidas wrote: The extra verboseness is fine, and I was almost finished posting a note that mentioned it. But I didn't thinking that the __printf0like bugs will never be fixed if we hide them by patching chmod. It was fixed more than a month ago: % RCS file: /home/ncvs/src/contrib/gcc/c-format.c,v % Working file: c-format.c % head: 1.4 % ... % % revision 1.3 % date: 2002/05/22 16:37:09; author: obrien; state: Exp; lines: +83 -6 % 1/2assed reimplementation of c-common.c revs 1.2 (-fformat-extensions) % and 1.3 (printf0) for GCC 3.1. % The printf0 part always worked on i386's and doesn't seem to have any machine dependencies. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
On Wednesday, July 10, 2002, at 05:22 PM, Matthew Dillon wrote: [snips] Personally speaking, as much as GCC annoys me it is sometimes better to modify the utility code then to add yet another hack to GCC that needs to be synchronized every time we update. -Matt Matthew Dillon [EMAIL PROTECTED] Amen! These hacks also place some things nearly out of reach (such as cross-compilability from Solaris). Just how _does_ one build a functional cross-toolchain for FreeBSD on a non-FreeBSD host? Cheers, Jerry Hicks [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Matthew Dillon wrote: : :Giorgos Keramidas [EMAIL PROTECTED] writes: : How does this look for fixing this warning? : :No, gcc should accept a NULL format string for err(3). It looks like :__printf0like is broken. : :DES :-- :Dag-Erling Smorgrav - [EMAIL PROTECTED] Oops. I've already starting changing the calls to err(). Please do not. gcc is just a tool. If it emits a warning on some arches because gcc doesn't understand how our libraries work, then we should disable the gcc checking for those arches on those functions. ie: remove the __printf0like completely for #ifdef sparc64 for err() etc. eg: --- cdefs.h 2002/07/08 16:43:35 1.56 +++ cdefs.h 2002/07/10 23:18:10 @@ -174,9 +174,9 @@ __attribute__((__format__ (__scanf__, fmtarg, firstvararg))) #endif /* Compiler-dependent macros that rely on FreeBSD-specific extensions. */ -#if __FreeBSD_cc_version = 31 +#if __FreeBSD_cc_version = 31 !defined(__sparc64__) #define__printf0like(fmtarg, firstvararg) \ __attribute__((__format__ (__printf0__, fmtarg, firstvararg))) #else #define__printf0like(fmtarg, firstvararg) This is much much less disruptive than slashing through userland and fixing something that is already perfectly correct and legal. Cheers, -Peter -- Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] All of this is for nothing if we don't go to the stars - JMS/B5 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav wrote:
Bruce Evans [EMAIL PROTECTED] writes:
The main bug is that the warning is emitted. err(1, NULL) is perfectly
valid (see err(4)). Apparently the sparc64 compiler is missing support
for __printf0like.
Strangely, my Alpha (July 3 -CURRENT) complains about this too, but my
i386 (June 24 -CURRENT) doesn't. Here's my test program:
#include stdio.h
int
main(void)
{
printf(NULL);
return 0;
}
on Alpha, I get
des@dsa ~% gcc -Wformat -c /tmp/format.c
/tmp/format.c: In function `main':
/tmp/format.c:6: warning: null format string
on i386, I don't get a warning.
Stranger and stranger.. On sparc64 from:
peter@panther[4:21pm]~-104 uname -a
FreeBSD panther.freebsd.org FreeBSD 5.0-CURRENT #2: Sun Jul 7 20:52:14 PDT 2002er
peter@panther[4:21pm]~-105 cat foo.c
#include stdio.h
#include err.h
int
main(void)
{
printf(NULL);
err(1, NULL);
return 0;
}
peter@panther[4:22pm]~-106 cc -O -Wformat -c foo.c
peter@panther[4:22pm]~-107
ie: it looks like it is completely disabled. Maybe the sparc64 tinderbox
host is simply out of sync with -current?
Cheers,
-Peter
--
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
All of this is for nothing if we don't go to the stars - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Peter Wemm [EMAIL PROTECTED] writes: [...] peter@panther[4:22pm]~-106 cc -O -Wformat -c foo.c peter@panther[4:22pm]~-107 ie: it looks like it is completely disabled. Maybe the sparc64 tinderbox host is simply out of sync with -current? It has a kernel/world of June 27, which seems to be the problem. I'll update the system today, but we should probably disable fatal warnings during the build/cross tools phase of world. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Thus spake Peter Wemm [EMAIL PROTECTED]: Please do not. gcc is just a tool. If it emits a warning on some arches because gcc doesn't understand how our libraries work, then we should disable the gcc checking for those arches on those functions. ie: remove the __printf0like completely for #ifdef sparc64 for err() etc. ... This is much much less disruptive than slashing through userland and fixing something that is already perfectly correct and legal. I agree that there's little sense in changing the code to work around a compiler bug, but it does not follow that the change is inherently a bad idea. I tend to think of adding descriptive error messages as something that should have been done long ago, and just happens to be slightly more useful now. The change buys us the time to figure out what's really wrong with gcc, rather than disabling and ignoring the offending warnings on sparc64. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Whoever fixes this, and however we agree to fix it, should also remember to close the bin/40382 PR. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Giorgos Keramidas [EMAIL PROTECTED] writes:
Whoever fixes this, and however we agree to fix it,
should also remember to close the bin/40382 PR.
Comments on the attached, untested patch?
Best regards,
Mike Barcroft
Disable fatal warnings during bootstrap, build, and cross tools
phase of world.
Index: Makefile.inc1
===
RCS file: /work/repo/src/Makefile.inc1,v
retrieving revision 1.294
diff -u -r1.294 Makefile.inc1
--- Makefile.inc1 1 Jul 2002 17:51:43 - 1.294
+++ Makefile.inc1 11 Jul 2002 04:50:02 -
@@ -589,8 +589,8 @@
${_cxx_consumers} gnu/usr.bin/texinfo
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
- ${MAKE} DIRPRFX=${_tool}/ depend; \
- ${MAKE} DIRPRFX=${_tool}/ all; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true depend; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true all; \
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX} install
.endfor
@@ -624,7 +624,8 @@
.for _tool in bin/csh bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \
${_libroken4} ${_libkrb5} lib/libncurses ${_share} \
usr.bin/awk usr.bin/file usr.sbin/sysinstall
- cd ${.CURDIR}/${_tool}; ${MAKE} DIRPRFX=${_tool}/ build-tools
+ cd ${.CURDIR}/${_tool}; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true build-tools
.endfor
#
@@ -650,8 +651,8 @@
gnu/usr.bin/cc ${_xlint}
cd ${.CURDIR}/${_tool}; \
${MAKE} DIRPRFX=${_tool}/ obj; \
- ${MAKE} DIRPRFX=${_tool}/ depend; \
- ${MAKE} DIRPRFX=${_tool}/ all; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true depend; \
+ ${MAKE} DIRPRFX=${_tool}/ NO_WERROR=true all; \
${MAKE} DIRPRFX=${_tool}/ DESTDIR=${MAKEOBJDIRPREFIX} install
.endfor
Re: sparc64 tinderbox failure
Bruce, On Thu, Jul 11, 2002 at 08:23:06AM +1000, Bruce Evans wrote: The extra verboseness is fine, and I was almost finished posting a note that mentioned it. But I didn't thinking that the __printf0like bugs will never be fixed if we hide them by patching chmod. It was fixed more than a month ago: sorry, -current from July, 10: === roadstone# cd /usr/src/bin/chmod/ roadstone# ls CVS Makefilechmod.1 chmod.c roadstone# make clean rm -f chmod chmod.o chmod.1.gz chmod.1.cat.gz roadstone# make cc -O -pipe -mcpu=ev5 -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wformat=2 -Wno-format-extra-args -Werror -c /net/storage/FreeBSD/src/bin/chmod/chmod.c cc1: warnings being treated as errors /net/storage/FreeBSD/src/bin/chmod/chmod.c: In function `main': /net/storage/FreeBSD/src/bin/chmod/chmod.c:174: warning: null format string *** Error code 1 Stop in /net/storage/FreeBSD/src/bin/chmod. roadstone# === Road Stone is Alpha AXP EV6 DECChip 21264 machine. The printf0 part always worked on i386's and doesn't seem to have any machine dependencies. I hope you are right. :) Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Would it be possible to get better granularity on when things like this are sent to the list? Maybe some flag to set that says, Hey, I started an actual buildworld, so from here on out any errors get mailed to the list. Doug On Mon, 8 Jul 2002, Dag-Erling Smorgrav wrote: Mon Jul 8 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Interrupted system call To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message -- We have known freedom's price. We have shown freedom's power. And in this great conflict, ... we will see freedom's victory. - George W. Bush, President of the United States State of the Union, January 28, 2002 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: -- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- /bin/sh:Permission denied Oops, this was the result of a conflict with my installworld. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: sparc64 tinderbox failure
Dag-Erling Smorgrav [EMAIL PROTECTED] writes: Thu Jun 13 07:00:00 GMT 2002 cvs [update aborted]: /home/ncvs/CVSROOT: Permission denied Mike, looks like the /work/repo isn't mounted on bowie. Can you fix this before the next run (7 am GMT tomorrow)? DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
