Date: Wed, 14 Mar 2007 08:27:38 +0100 (CET) From: linimon@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <20070314072738.566D91CD12@mail.droso.net>
next in thread | raw e-mail | index | archive | help
Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we are attempting to notify maintainers of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc3.4, which is much stricter about such things as function declarations, literal strings constants that continue over several physical lines, and forcing the deprecation of antique header files such as varargs.h (we should now be using stdargs.h). The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. If you need help in one or more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 4.x/5.x/6.x with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: biology/biojava broken because: Does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007030306/biojava-1.5.b,1.log (Mar 5 03:36:11 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=biojava portname: biology/tinker broken because: Unfetchable build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007022216/tinker-4.2.20040908_1.log (Feb 26 20:10:06 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=tinker portname: chinese/gbfs broken because: fails to patch - Included patches are broken build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=gbfs portname: chinese/tatter-tools broken because: Incorrect pkg-plist build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007031101/zh-tatter-tools-1.0.6.1.log (Mar 4 14:41:17 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=tatter-tools portname: chinese/xemacs broken because: Does not build even with fix for -lxpg4 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.5.2007021416/zh-xemacs-20.4_2.log (Feb 9 16:46:27 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=xemacs portname: databases/postgis-jdbc broken because: Does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007022216/postgis-jdbc-1.1.1.log (Feb 26 17:48:32 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgis-jdbc portname: deskutils/yank broken because: Incomplete pkg-plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=yank portname: devel/php-dbg broken because: Does not compile build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.2007022216/php-dbg-2.11.30.log (Mar 2 11:50:04 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=php-dbg portname: games/hlserver-cs broken because: Incomplete fetch instructions build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=hlserver-cs portname: games/hlserver-dod broken because: Incomplete fetch instructions build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=hlserver-dod portname: japanese/gnomelibs broken because: Does not compile on FreeBSD 5.X and above build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007030306/ja-gnome-libs-1.4.2_6.log (Mar 4 22:20:45 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=gnomelibs portname: japanese/lookup-xemacs broken because: Does not install build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.5.2006091522/ja-lookup-xemacs21-mule-1.4_1.log (Oct 6 23:11:44 UTC 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=lookup-xemacs portname: japanese/lynx broken because: Leaves behind config file on deinstall build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=lynx portname: japanese/ptex broken because: Does not build (uses DESTDIR internally) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=ptex portname: multimedia/ogmrip broken because: Incorrect pkg-plist build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.5.2007030602/ogmrip-0.10.2.log (Mar 11 01:55:26 UTC 2007) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.2007022216/ogmrip-0.10.2.log (Feb 26 20:13:37 UTC 2007) http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.2006122818/ogmrip-0.10.0.r4_1.log (Jan 15 22:09:58 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=ogmrip portname: net-mgmt/cflowd broken because: Does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007031101/cflowd-2.1.b1_9,1.log (Mar 4 07:21:43 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=cflowd portname: net-mgmt/sting broken because: Does not work with ipfw2 build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.5.2006121119/sting-0.7.log.bz2 (Mar 14 23:43:11 UTC 2006) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007030306/sting-0.7.log (Mar 4 01:39:19 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=sting portname: net/linphone-base broken because: broken by latest update to libosip2 build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.2007022216/linphone-base-1.3.5,1.log (Mar 2 16:28:04 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=linphone-base portname: palm/malsync broken because: Does not build with new pilot-link build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007030306/malsync-2.20_1.log (Mar 4 08:07:59 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=malsync portname: palm/synce-trayicon broken because: Configure fails build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.2007022216/synce-trayicon-0.9.0_5.log (Mar 2 16:40:25 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=palm&portname=synce-trayicon portname: russian/elm.language broken because: Leaves behind files on deinstall build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=russian&portname=elm.language portname: russian/pine.language broken because: Leaves behind config file on deinstall build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=russian&portname=pine.language portname: textproc/ocaml-yaxi broken because: Does not build build errors: http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.2007022216/ocaml-yaxi-0.5.3.log (Mar 2 16:14:30 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=ocaml-yaxi portname: textproc/ruby-libxslt broken because: Configure fails on FreeBSD >= 5.x build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007030306/ruby18-libxslt-0.3.0_1.log (Mar 4 10:15:10 UTC 2007) overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=ruby-libxslt portname: www/p5-Apache-AuthenCache broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=p5-Apache-AuthenCache portname: www/rt3 broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt3 portname: www/rt32 broken because: Broken due the new mod_perl2 API build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt32 portname: www/urchin5 broken because: Does not install build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.6.2007031101/urchin-5.703.log ( ) http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.4.2007020105/urchin-5.703.log.bz2 (Sep 13 20:13:16 GMT 2006) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=urchin5 If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon <linimon@FreeBSD.org>, so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070314072738.566D91CD12>