Re: FreeBSD build status
On Thu, 27 Apr 2000, Poul-Henning Kamp wrote: === SUMMARY === World ***didn't compile*** 3 Warnings Kernel LINT compiled 147 Warnings LINT has been broken for a long time by depenencies on optional crypto sources (sys/crypto). The IPSEC options have required crypto sources for a long time. Now the NETGRQAPH_MPCC_ENCRYPTION option requires them. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD build status
On Thursday, 27 April 2000 at 22:04:19 +0200, Poul-Henning Kamp wrote: This looks a lot better. Greg === SUMMARY === World ***didn't compile*** 3 Warnings Kernel LINT compiled 147 Warnings Kernel GENERIC compiled 58 Warnings Kernel GENERIC98 ***didn't compile*** 63 Warnings === Compile errors for kernel GENERIC98 === cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../pc98/pc98/wd_cd.c In file included from ../../pc98/pc98/wd_cd.c:44: ../../pc98/pc98/wormio.h:9: warning: `/*' within comment ../../pc98/pc98/wormio.h:117: unbalanced `#endif' *** Error code 1 (continuing) `all' not remade because of errors. === Compile errors from make world === cd /otte/src/games/phantasia; make build-tools cc -O -pipe -c -o cross-phantglobs.o /otte/src/games/phantasia/phantglobs.c cc -O -pipe -c /otte/src/games/phantasia/setup.c cc -static -O -pipe-o setup cross-phantglobs.o setup.o -lm cd /otte/src/gnu/usr.bin/gperf; make build-tools make: don't know how to make build-tools. Stop *** Error code 2 Stop in /otte/src. *** Error code 1 Stop in /otte/src. *** Error code 1 Stop in /otte/src. -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD build status
=== SUMMARY === World ***didn't compile*** 3 Warnings Kernel LINT compiled 147 Warnings Kernel GENERIC compiled 58 Warnings Kernel GENERIC98 ***didn't compile*** 63 Warnings === Compile errors for kernel GENERIC98 === cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../pc98/pc98/wd_cd.c In file included from ../../pc98/pc98/wd_cd.c:44: ../../pc98/pc98/wormio.h:9: warning: `/*' within comment ../../pc98/pc98/wormio.h:117: unbalanced `#endif' *** Error code 1 (continuing) `all' not remade because of errors. === Compile errors from make world === cd /otte/src/games/phantasia; make build-tools cc -O -pipe -c -o cross-phantglobs.o /otte/src/games/phantasia/phantglobs.c cc -O -pipe -c /otte/src/games/phantasia/setup.c cc -static -O -pipe-o setup cross-phantglobs.o setup.o -lm cd /otte/src/gnu/usr.bin/gperf; make build-tools make: don't know how to make build-tools. Stop *** Error code 2 Stop in /otte/src. *** Error code 1 Stop in /otte/src. *** Error code 1 Stop in /otte/src. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD build status
=== SUMMARY === World compiled 637 Warnings 45 Errors Kernel LINT compiled 149 Warnings 0 Errors Kernel GENERIC compiled 59 Warnings 0 Errors Kernel GENERIC98 ***didn't compile*** 54 Warnings 0 Errors === Compile errors for kernel GENERIC98 === cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../pc98/i386/machdep.c ../../pc98/i386/machdep.c:129: machine/random.h: No such file or directory *** Error code 1 (continuing) cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../pc98/pc98/syscons.c ../../pc98/pc98/syscons.c:58: machine/random.h: No such file or directory *** Error code 1 (continuing) `all' not remade because of errors. === All warnings from kernel LINT === ../../dev/amr/amr.c:1022: warning: `amr_wait_command' defined but not used ../../dev/amr/amr.c:1225: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1525: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1556: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type ../../dev/amr/amr.c:687: warning: unused variable `i' ../../dev/amr/amr.c:687: warning: unused variable `s' ../../dev/awi/if_awi_pccard.c:115: warning: assignment discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:1295: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:500: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:611: warning: cast discards qualifiers from pointer target type ../../dev/ex/if_ex.c:1150: warning: unused variable `sc' ../../dev/fb/vga.c:1321: warning: `fill' defined but not used ../../dev/fb/vga.c:1331: warning: `filll_io' defined but not used ../../dev/hea/eni_buffer.c:115: warning: cast discards qualifiers from pointer target type ../../dev/hea/eni_vcm.c:279: warning: cast discards qualifiers from pointer target type ../../dev/hfa/fore_buffer.c:751: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_command.c:440: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200E' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_UNKNOWN' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_FORE_SBA200E' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_UNKNOWN' not handled in switch ../../dev/hfa/fore_receive.c:562: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_transmit.c:343: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1236: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1325: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1325: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1342: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1354: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1399: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1537: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1551: warning: cast discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1605: warning: passing arg 1 of pointer to function discards qualifiers from pointer target type ../../dev/ie/if_ie.c:1614:
Re: FreeBSD build status
In message [EMAIL PROTECTED], Andrzej Bialecki writes: On Tue, 25 Apr 2000, Poul-Henning Kamp wrote: === SUMMARY === [27kB long list of errors deleted..] I thought that the final conclusion was to have some other mailing list for this type of messages... ? I don't think there were any final conclusion, so I'm selectively forwarding it whenever something is broken. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD build status
The summary may have saved lots of net time. I did not cvsup today because of the summary. tomdean To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD build status
=== SUMMARY === World compiled 637 Warnings 45 Errors Kernel LINT compiled 149 Warnings 0 Errors Kernel GENERIC compiled 59 Warnings 0 Errors Kernel GENERIC98 ***didn't compile*** 54 Warnings 0 Errors This doesn't look right I count two :) -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD build status
In message [EMAIL PROTECTED], Brian Somers writes: === SUMMARY === World compiled 637 Warnings 45 Errors Kernel LINT compiled 149 Warnings 0 Errors Kernel GENERIC compiled 59 Warnings 0 Errors Kernel GENERIC98 ***didn't compile*** 54 Warnings 0 Errors This doesn't look right I count two :) Uhm, Right, I'd better check my script :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD build status
On Tuesday, 25 April 2000 at 18:09:00 +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Andrzej Bialecki writes: On Tue, 25 Apr 2000, Poul-Henning Kamp wrote: === SUMMARY === [27kB long list of errors deleted..] I thought that the final conclusion was to have some other mailing list for this type of messages... ? I don't think there were any final conclusion, so I'm selectively forwarding it whenever something is broken. Could you be more selective? This appears to affect only GENERIC98, but the other stuff could be misleading. On Tuesday, 25 April 2000 at 10:28:23 -0700, Thomas Dean wrote: The summary may have saved lots of net time. I did not cvsup today because of the summary. I think you were one of the misled, unless you use PC98. Greg -- Finger [EMAIL PROTECTED] for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED], Warner Losh writes: It isn't something specific to Poul's system. I've recreated it here as well. I've also tracked it down to the -fno-builtin that is in LINT, but not in GENERIC. Now, to think about what to do about it... It is to be left there to catch people who use functions which are not in the kernel, but which gcc implements as built-ins :-) -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? Becuase it's chunky and regular enough that I don't see why we also can't just create a new notification service for it. Think a bit bigger-picture also; theoretically, we should have these reports for -current and the RELENG_3 and RELENG_4 branches. The machine-resources are available for it, we just haven't organized it properly. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED], Peter Jeremy write s: IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). I agree. Comments: - I hope it has a well-defined subject so it can be easily recognized. "FreeBSD Build status" - I presume it's built using the default make.conf. Yes. - It would be nice if it reported changes since the previous day (or successful build). This would make it easier to see what has been broken recently. Well, it reports on sundays and if anything doesn't build. If it reports, it includes the errors which from the non-building components and "New warnings in *" delta lists relative to the previous report. I've sorted the report so that the most interesting things are at the top. Other ideas welcome. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
In message [EMAIL PROTECTED], "Jordan K. Hubbard" writes: IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? Becuase it's chunky and regular enough that I don't see why we also can't just create a new notification service for it. Because the people who don't compile LINT are unlikely to subscribe to it. The alternative is to send it to committers, but I pressume all the ports people would be pretty annoyed, and by sending it to -current maybe a new junior hacker or two could be ferret out :-) Think a bit bigger-picture also; theoretically, we should have these reports for -current and the RELENG_3 and RELENG_4 branches. The machine-resources are available for it, we just haven't organized it properly. That makes sense. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
Comments: - I hope it has a well-defined subject so it can be easily recognized. "FreeBSD Build status" Procmail is your friend... A lot of the list message I receive get bounced to a lower-priority-that-I-have-to-read-these folder, but anything with "HEADS-UP"(?) gets sent to my primary folder. My vote is that this is A Good Idea. mike To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, 18 Apr 2000, Peter Jeremy wrote: On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" [EMAIL PROTECTED] wrote: As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). It *IS* a bad idea. Consider how big the failure report can be. Why not instead: 1) have the report automatically uploaded on web 2) have the summary of summaries be sent to -current The summary of summaries would roughly look like this: Subject: -current build report Success: world, generic Fail: lint For details, see http://blah.foo.bar/FreeBSD-build/date It conveys the information most needed, and can hardly hurt anybody's mailbox. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, 18 Apr 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Peter Jeremy write s: IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). I agree. As one of those who pays for an incoming traffic I'm prefer a short letter with a list of directories where warning/errors happens and an URL with full listing. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED], Nar vi writes: The summary of summaries would roughly look like this: Subject: -current build report Success: world, generic Fail: lint The First part of the email is a summary just like that. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
On Tue, 18 Apr 2000, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], Nar vi writes: The summary of summaries would roughly look like this: Subject: -current build report Success: world, generic Fail: lint The First part of the email is a summary just like that. See what Boris Popov writes on the issue. I am sure there are more people who think that a big status report is not cost effective, if they can get a *short* summary, and an url where they can get the full report. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
In message [EMAIL PROTECTED], Nar vi writes: The summary of summaries would roughly look like this: Subject: -current build report Success: world, generic Fail: lint The First part of the email is a summary just like that. See what Boris Popov writes on the issue. I am sure there are more people who think that a big status report is not cost effective, if they can get a *short* summary, and an url where they can get the full report. Listen, we are talking about an email which is shorter than the list of open PRs, and if people actually *DO* something about it it will get shorter fast The only reason it is a long report right now is that people are sloppy! -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
On Tue, Apr 18, 2000 at 08:38:47AM +0200, Poul-Henning Kamp wrote: In message [EMAIL PROTECTED], "Jordan K. Hubbard" writes: IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? Becuase it's chunky and regular enough that I don't see why we also can't just create a new notification service for it. Because the people who don't compile LINT are unlikely to subscribe to it. The alternative is to send it to committers, but I pressume all the ports people would be pretty annoyed, and by sending it to -current maybe a new junior hacker or two could be ferret out :-) Think a bit bigger-picture also; theoretically, we should have these reports for -current and the RELENG_3 and RELENG_4 branches. The machine-resources are available for it, we just haven't organized it properly. I think reports for RELENG_3 and RELENG_4 should be sent to -stable rather than here, and sent only if something doesn't build or new warnings appear wrt the previous build; this should be rare enough not to bother -stable people and anyone MFCing should be reading -stable anyway? And I think sending -current reports here is a *great* idea and including kernel builds, not just make world, is also very good. Just my $0.02. -- Anatoly Vorobey, [EMAIL PROTECTED] http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, Apr 18, 2000 at 09:48:11AM +0200, Poul-Henning Kamp wrote: Listen, we are talking about an email which is shorter than the list of open PRs, and if people actually *DO* something about it it will get shorter fast The only reason it is a long report right now is that people are sloppy! I have large amounts of patches that fix a lot of these. They were done by myself and Nathan Ahlstrom. I'm currently making sure that they don't trade warning fixes for style errors, and I will start committing them. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: [EMAIL PROTECTED] / [EMAIL PROTECTED] Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
FreeBSD Build status
I have a machine which isn't doing much right now, so I have decided to set it up as an automatic "FreeBSD Build checker". Once per day the machine cvsups, checks out a virgin source tree, tries to build GENERIC, GENERIC98, LINT and world. If any of these builds fail it will send a report like this. On Sundays the report will always be sent. Once I have this tested a bit more, I will start mailing the the reports directly to [EMAIL PROTECTED] It is not shown here, but a delta listing whining about new warnings in any of the builds is also featured. Poul-Henning --- Forwarded Message Date: Mon, 17 Apr 2000 23:09:06 +0200 (CEST) Message-Id: [EMAIL PROTECTED] Subject: FreeBSD build status From: Build-o-matic [EMAIL PROTECTED] To: undisclosed-recipients:; --- SUMMARY --- World compiled 637 Warnings 45 Errors Kernel LINT ***didn't compile*** 150 Warnings 0 Errors Kernel GENERIC compiled 59 Warnings 0 Errors Kernel GENERIC98 compiled 54 Warnings 0 Errors --- Compile errors for kernel LINT --- linking kernel awi.o: In function `awi_ioctl': awi.o(.text+0x3b4): undefined reference to `memcmp' awi.o(.text+0x3cf): undefined reference to `memset' awi.o: In function `awi_drvset': awi.o(.text+0x74f): undefined reference to `memcmp' awi.o(.text+0x76a): undefined reference to `memset' awi.o: In function `awi_input': awi.o(.text+0x1499): undefined reference to `memcmp' awi.o: In function `awi_init_hw': awi.o(.text+0x1c8a): undefined reference to `memcmp' awi.o: In function `awi_init_mibs': awi.o(.text+0x1e96): undefined reference to `memset' awi.o: In function `awi_start_scan': awi.o(.text+0x22f5): undefined reference to `memset' awi.o: In function `awi_stop_scan': awi.o(.text+0x24e3): undefined reference to `memcmp' awi.o: In function `awi_recv_beacon': awi.o(.text+0x266b): undefined reference to `memcmp' awi.o(.text+0x2681): undefined reference to `memcmp' awi.o(.text+0x26f8): undefined reference to `memset' awi.o: In function `awi_recv_auth': awi.o(.text+0x2e68): undefined reference to `memcmp' awi.o: In function `awi_recv_asresp': awi.o(.text+0x31d8): undefined reference to `memcmp' if_awi_pccard.o: In function `awi_pccard_probe': if_awi_pccard.o(.text+0xac): undefined reference to `memcmp' isa_compat.o(.data+0x14): undefined reference to `vtdriver' *** Error code 1 (continuing) `all' not remade because of errors. --- All warnings from kernel LINT --- ../../dev/amr/amr.c:1015: warning: `amr_wait_command' defined but not used ../../dev/amr/amr.c:1218: warning: passing arg 2 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1518: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:1549: warning: passing arg 1 of `bcopy' discards qualifiers from pointer target type ../../dev/amr/amr.c:171: warning: cast discards qualifiers from pointer target type ../../dev/awi/awi.c:505: warning: implicit declaration of function `memcmp' ../../dev/awi/awi.c:508: warning: implicit declaration of function `memset' ../../dev/awi/if_awi_pccard.c:115: warning: assignment discards qualifiers from pointer target type ../../dev/awi/if_awi_pccard.c:90: warning: implicit declaration of function `memcmp' ../../dev/dpt/dpt_scsi.c:1296: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:501: warning: cast discards qualifiers from pointer target type ../../dev/dpt/dpt_scsi.c:612: warning: cast discards qualifiers from pointer target type ../../dev/ex/if_ex.c:1151: warning: unused variable `sc' ../../dev/fb/vga.c:1321: warning: `fill' defined but not used ../../dev/fb/vga.c:1331: warning: `filll_io' defined but not used ../../dev/hea/eni_buffer.c:115: warning: cast discards qualifiers from pointer target type ../../dev/hea/eni_vcm.c:279: warning: cast discards qualifiers from pointer target type ../../dev/hfa/fore_buffer.c:751: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_command.c:440: warning: passing arg 1 of `atm_dev_free' discards qualifiers from pointer target type ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_FORE_SBA200E' not handled in switch ../../dev/hfa/fore_intr.c:165: warning: enumeration value `DEV_UNKNOWN' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_ENI_155P' not handled in switch ../../dev/hfa/fore_load.c:1361: warning: enumeration value `DEV_FORE_SBA200' not handled in switch ../../dev/hfa/fore_l
Re: FreeBSD Build status
I have a machine which isn't doing much right now, so I have decided to set it up as an automatic "FreeBSD Build checker". Welcome to the current.freebsd.org game. :) Once per day the machine cvsups, checks out a virgin source tree, tries to build GENERIC, GENERIC98, LINT and world. If any of these builds fail it will send a report like this. On Sundays the report will always be sent. Once I have this tested a bit more, I will start mailing the the reports directly to [EMAIL PROTECTED] And now we get into a slightly twitchy area... These error messages can be quite long and annoying, far too detailed for the likes of the -current mailing list, which is why I've been sending them only to an opt-in alias called "[EMAIL PROTECTED]" which sends a success/failure summary like yours and include the last 100 lines of failure output for debugging. It also does this for both the RELENG_4 branch and -current. That said, I've also done a singularly bad job of actually letting people know that build-reports even exists so I wouldn't expect you or anyone else (except maybe Bill Paul) to have known about it. It's just an alias on hub.freebsd.org right now and not a real majordomo-managed mailing list, so I wasn't inclined to take on the workload of managing the alias. It does at least log its results to the build-reports mail archive so anyone looking in /home/mail/build-reports on hub can also spy on the current status of both active branches. If there's a real interest in this, then this should obviously be created as a real mailing list and probably split into build-reports-stable and build-reports-current for people who only want one or the other. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
Hi,
I have a patch against these warnings. They are the result of a function
being called with a pointer to a function rather than a string...
/otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655:
warning: passing arg 1 of `warning' from incompatible pointer type
/otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1655:
warning: passing arg 1 of `warning' from incompatible pointer type
/otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678:
warning: passing arg 1 of `warning' from incompatible pointer type
/otte/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/c-common.c:1678:
warning: passing arg 1 of `warning' from incompatible pointer type
The patch:
--- c-common.c.orig Mon Nov 1 13:41:09 1999
+++ c-common.c Sat Apr 8 06:32:52 2000
@@ -1652,7 +1652,7 @@
/* There should be an int arg to control the string arg. */
if (params == 0)
{
- warning (tfaff);
+ tfaff ();
return;
}
if (info-first_arg_num != 0)
@@ -1675,7 +1675,7 @@
/* There should be an unsigned char * arg before the string arg. */
if (params == 0)
{
- warning (tfaff);
+ tfaff ();
return;
}
if (info-first_arg_num != 0)
Should I just send a PR ?
Patrick.
c-common.c.patch
Re: FreeBSD Build status
In message [EMAIL PROTECTED], "Jordan K. Hubbard" writes: That said, I've also done a singularly bad job of actually letting people know that build-reports even exists so I wouldn't expect you or anyone else (except maybe Bill Paul) to have known about it. It's just an alias on hub.freebsd.org right now and not a real majordomo-managed mailing list, so I wasn't inclined to take on the workload of managing the alias. It does at least log its results to the build-reports mail archive so anyone looking in /home/mail/build-reports on hub can also spy on the current status of both active branches. But does this also check the kernels ? It was my understanding that it only did world/release ? As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
In message [EMAIL PROTECTED] Poul-Henning Kamp writes: : awi.o(.text+0x3b4): undefined reference to `memcmp' : awi.o(.text+0x3cf): undefined reference to `memset' What I want to know is why I don't get these with the GENERIC + awi config file I have :-( Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED], Warner Losh writes: In message [EMAIL PROTECTED] Poul-Henning Kamp writes: : awi.o(.text+0x3b4): undefined reference to `memcmp' : awi.o(.text+0x3cf): undefined reference to `memset' What I want to know is why I don't get these with the GENERIC + awi config file I have :-( That is probably a Bruce question, but I would suspect that LINT is more paranoid about disabling GCC builtins ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD coreteam member | 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: FreeBSD Build status
But does this also check the kernels ? It was my understanding that it only did world/release ? It only does the world/release (and it's the chrooted make release "world build" which is reported on, not the host system's BTW) but could easily add a kernel build just for the benefit of the mailing list folks. It would be trivial to add. As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious (and daily) and -current was never created as a place for daemons to talk to people in any case, it was created as a discussion forum. Let's do this, by all means, but let's plase do it elsewhere. Anyone who starts sending daily automated anythings to any of our "top level" mailing lists will classify themselves as a spammer on my and many other people's radar. - Jordan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
: awi.o(.text+0x3b4): undefined reference to `memcmp' : awi.o(.text+0x3cf): undefined reference to `memset' What I want to know is why I don't get these with the GENERIC + awi config file I have :-( Are you compiling with optimization turned on? I believe mem* are inlined if optimization is enabled. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED] Nate Williams writes: : Are you compiling with optimization turned on? I believe mem* are : inlined if optimization is enabled. Don't think so. Both build -O. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
: Are you compiling with optimization turned on? I believe mem* are : inlined if optimization is enabled. Don't think so. Both build -O. Poul's build may not have optimization turned on, since it's controlled by /etc/make.conf. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED] Nate Williams writes: : : Are you compiling with optimization turned on? I believe mem* are : : inlined if optimization is enabled. : : Don't think so. Both build -O. : : Poul's build may not have optimization turned on, since it's controlled : by /etc/make.conf. It isn't something specific to Poul's system. I've recreated it here as well. I've also tracked it down to the -fno-builtin that is in LINT, but not in GENERIC. Now, to think about what to do about it... Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
: : Are you compiling with optimization turned on? I believe mem* are : : inlined if optimization is enabled. : : Don't think so. Both build -O. : : Poul's build may not have optimization turned on, since it's controlled : by /etc/make.conf. It isn't something specific to Poul's system. I've recreated it here as well. I've also tracked it down to the -fno-builtin that is in LINT, but not in GENERIC. Now, to think about what to do about it... I thought that the use of mem* and friends violated KNF. Nate To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
In message [EMAIL PROTECTED] Nate Williams writes: : I thought that the use of mem* and friends violated KNF. They do, iirc. However, this driver tries to be maximally portable and choses to use the NetBSD convention. I've added compat code so that differences between the two drivers can be held to a minimum. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
LINT is now building again. I went ahead and fixed the vtdriver not defined problem by removing it from isa_comapt.h. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Mon, Apr 17, 2000 at 11:17:15PM +0200, Poul-Henning Kamp wrote: Once per day the machine cvsups, checks out a virgin source tree, tries to build GENERIC, GENERIC98, LINT and world. If any of these builds fail it will send a report like this. On Sundays the report will always be sent. Are any of these warnings of the "helpful gcc" type, rather than actual dangers? It would be a shame if this resulted in obfuscation of the code base _just_ to shut gcc up. Of course if gcc is well-behaved on this point, and the warning flags are well sorted and agreed-upon, then there isn't a problem. -- Andrew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Mon, Apr 17, 2000 at 05:51:35PM -0400, Patrick Bihan-Faou wrote: I have a patch against these warnings. They are the result of a function being called with a pointer to a function rather than a string... ...snip... Should I just send a PR ? You should send a PR to the GCC developers, not us for this. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
"Jordan K. Hubbard" wrote: But does this also check the kernels ? It was my understanding that it only did world/release ? It only does the world/release (and it's the chrooted make release "world build" which is reported on, not the host system's BTW) but could easily add a kernel build just for the benefit of the mailing list folks. It would be trivial to add. As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious (and daily) and -current was never created as a place for daemons to talk to people in any case, it was created as a discussion forum. Let's do this, by all means, but let's plase do it elsewhere. Anyone who starts sending daily automated anythings to any of our "top level" mailing lists will classify themselves as a spammer on my and many other people's radar. Not sure I agree with the annoyance issue. It's already got a few people thinking about some of the issues so I think it's useful. If we lose some readers of -current because a report of development problems is too much for them then they probably shouldn't be -current subscribers in the first place. Hackers is supposed to be the mailing list for people generally interested in hacking on FreeBSD, current *should* be for people who want to see long tedious reports on the problems in the current branch. Also, the length of the report should fall dramatically as the problems are addressed and a sudden long report will immediately focus developers attention to the cause. Paul. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, Apr 18, 2000 at 01:45:57PM +1000, Bruce Evans wrote: Should I just send a PR ? No, there is already a PR for this (15549). Doh! The problem is in our code, not the FSF code. Fixed. -- -- David([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" [EMAIL PROTECTED] wrote: As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). Comments: - I hope it has a well-defined subject so it can be easily recognized. - I presume it's built using the default make.conf. - It would be nice if it reported changes since the previous day (or successful build). This would make it easier to see what has been broken recently. Peter To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: FreeBSD Build status
On Tue, Apr 18, 2000 at 03:25:35PM +1000, Peter Jeremy wrote: On 2000-Apr-18 08:07:45 +1000, "Jordan K. Hubbard" [EMAIL PROTECTED] wrote: As for the lists being tedious and long: I've sorted the content by relevance, and it was my hope that over time they would shrink to zero if we annoyed people enough with them. I think that's too much annoyance, really. I can see most people simply unsubscribing from -current in the face of a mail that long and tedious IMHO, it's not such a bad idea. freebsd-current _is_ the place to report problems with -current, why can't the report be produced by a daemon? All the MUA's I've ever used allowed me to delete a mail before reading all of it, so I don't see that having detailed information (at the end) is a real issue (though it might be for someove paying by the byte). Sorry that I just chime in, but wouldn't it be more appropriate to go for a system similar to the one at mozilla.org? They do pretty much the same things that have been discussed here, but it looks so cl... and does not bother people on normal mailing lists. They have tinderbox.mozilla.org, which always inidcates current build status on a number of machines (and OS-es) the log is available too. And it is integrated with the CVS system so you can see at once what commits have been made since the last build attempt, etc. Maybe we could adapt this system to our needs? (they do not bother about warnings, for example.) Just my thoughts... Regards: Szilveszter ADAM Szeged University Szeged Hungary To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
