On Tue, 11 Nov 2014 20:21:48 +0100 Dimitry Andric <d...@freebsd.org> wrote
> On 11 Nov 2014, at 20:04, Chris H <bsd-li...@bsdforge.com> wrote: > ... > > But sadly. blowing away ports, src, and obj. Then checking out > > src r274382, and performing a buildworld. Although I got further. > > it bombed at: > > > > ===> usr.sbin/hyperv (all) > > ===> usr.sbin/hyperv/tools (all) > > cc -O2 -pipe > > -I/usr/src/usr.sbin/hyperv/tools/../../../sys/dev/hyperv/utiliti > > es -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall > > -Wno-format-y2k - > > W -Wno-unused-parameter -Wstrict-prototypes -Wmissing-prototypes > > -Wpointer-arith > > -Wreturn-type -Wcast-qual -Wwrite-strings -Wswitch -Wshadow > > -Wunused-parameter -Wcast-align -Wchar-subscripts -Winline -Wnested-externs > > -Wredundant-decls -Wold > > -style-definition -Wno-pointer-sign -c > > /usr/src/usr.sbin/hyperv/tools/../../.. > > /contrib/hyperv/tools/hv_kvp_daemon.c > > cc1: warnings being treated as errors > > > > /usr/src/usr.sbin/hyperv/tools/../../../contrib/hyperv/tools/hv_kvp_daemon.c: > > In > > function 'kvp_get_ip_info': > > > > /usr/src/usr.sbin/hyperv/tools/../../../contrib/hyperv/tools/hv_kvp_daemon.c: > > 814 : warning: 'ip_buffer' may be used uninitialized in this function > > Yep, this is another false positive from gcc. I've mailed a proposed > workaround to Xin Li, but for now, if you compile world and kernel with > gcc, use NO_WERROR= and WERROR= in your make.conf. Especially the > kernel still needs a bunch of fixes to make it work with gcc again. > > It's a pity the gcc tinderboxes have been taken offline. Maybe this can > be added to the FreeBSD Jenkins instance now? Thank you *very* much, Dimitry. For the informative reply. Yes. I agree, adding a task for Jenkins seems like a *very* good idea. Well, it looks like a real gamble not going with defaults, for now. I guess attempts using gcc as base compiler is off the table, for now. This must really hit some of the other ARCHS pretty hard. I can't imagine trying to develop under these circumstances. Here's hoping for improvements in this area soon! Thanks again, Dimitry. --Chris > > -Dimitry _______________________________________________ firstname.lastname@example.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"