On Sun, Nov 11, 2018 at 08:03:34AM -0700, lan...@openbsd.org wrote: > bulk build on sparc64-1.ports.openbsd.org > started on Thu Nov 1 03:12:31 MDT 2018 > finished at Sun Nov 11 08:03:15 MST 2018 > lasted 10D22h50m > done with kern.version=OpenBSD 6.4-current (GENERIC) #21: Wed Oct 31 18:29:44 > MDT 2018 > > built packages:7980 > Nov 1:6536 > Nov 2:319 > Nov 3:154 > Nov 4:64 > Nov 5:63 > Nov 6:103 > Nov 7:124 > Nov 8:216 > Nov 9:400 > Nov 10:1098 > Nov 11:1896 > > > critical path missing pkgs: > http://build-failures.rhaalovely.net//sparc64/2018-11-01/summary.log
For the ones caring a bit about sparc64, this bulk has many "new" failures for the following reasons: - all c++ code is now built with lang/gcc/4.9, which is much stricter on headers/declarations - the summary.log link above shows that databases/mariadb and textproc/aspell/core are the ones broken which take out most non-built paths: qt3, qt4, php.. and all the ones depending on it. If you fix those two ports, you can unlock many other ports. - i'll select a few failures in the list below to show ports@ submitters the kind of errors which happen on sparc64, and how one can submit a fix for them.. > http://build-failures.rhaalovely.net//sparc64/2018-11-01/cad/necpp.log c_geometry.cpp:2311:49: error: 'atoi' was not declared in this scope missing include ? > http://build-failures.rhaalovely.net//sparc64/2018-11-01/devel/ccrtp.log In file included from source.cpp:45:0: ./ccrtp/sources.h:409:11: error: 'ptrdiff_t' does not name a type missing include ? > http://build-failures.rhaalovely.net//sparc64/2018-11-01/graphics/imv.log /usr/local/lib/libfreeimage.so.2.0: undefined reference to `std::__detail::_List_node_base::_M_unhook()' uses c++11 ? > http://build-failures.rhaalovely.net//sparc64/2018-11-01/misc/cdrdao,audio.log FormatConverter.cc:64:36: error: 'strrchr' was not declared in this scope missing string.h > http://build-failures.rhaalovely.net//sparc64/2018-11-01/net/py-slixmpp.log slixmpp/stringprep.c:583:24: error: stringprep.h: No such file or directory missing string.h > http://build-failures.rhaalovely.net//sparc64/2018-11-01/x11/blackbox.log Image.cc:1350:42: error: 'memcpy' was not declared in this scope missing #include <string.h> as you can see, fixing those failures is not so hard, it just needs time. You can even help by trying on amd64 to build with ports-gcc by changing the COMPILER line, reproduce the failure, patch it, and retry. The next bulk will probably be even worse, as we might try using lang/gcc/6 there. so fixing a bunch of the existing breakage first would be nice.. for that, fixes from contributors are welcome :) Landry
