From owner-freebsd-ports@FreeBSD.ORG Fri Mar 7 08:28:08 2014 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBD29736 for ; Fri, 7 Mar 2014 08:28:08 +0000 (UTC) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB927CEA for ; Fri, 7 Mar 2014 08:28:08 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.8/8.14.8) with ESMTP id s278S8Qv075484 for ; Fri, 7 Mar 2014 08:28:08 GMT (envelope-from linimon@FreeBSD.org) Date: Fri, 7 Mar 2014 08:28:08 GMT Message-Id: <201403070828.s278S8Qv075484@portsmon.freebsd.org> From: linimon@FreeBSD.org To: ports@FreeBSD.org Subject: FreeBSD ports which are currently marked broken X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 08:28:09 -0000 As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users 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 gcc4.2, which is much stricter than older versions. 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. 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 7.x/8.x/9.x/-current 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: audio/ruby-esound broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=ruby-esound portname: chinese/hztty broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty portname: databases/py-fdb broken because: Does not compile on FreeBSD 9 i386 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=py-fdb portname: devel/buildapp broken because: require needs a pathname for uninstalled modules with the ASDF 3.x bundled with sbcl build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=buildapp portname: games/mangos broken because: Fails with newer autotools build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=mangos portname: games/sumwars broken because: Fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=sumwars portname: games/tyrquake broken because: Fails to build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=tyrquake portname: graphics/py-poppler-qt4 broken because: Doesn't build with current poppler API build errors: http://beefy2.isc.freebsd.org/bulk/10-release-amd64-RELENG10_0/latest/logs/errors/py27-poppler-qt4-0.16.3_2.log ((not currently populated)) overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=py-poppler-qt4 portname: korean/eterm broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=korean&portname=eterm portname: mail/biffer broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=biffer portname: net-im/centericq broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=centericq portname: net-im/ysm broken because: Fails to install build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=ysm portname: net-mgmt/sendip broken because: does not compile on FreeBSD 9.X build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-mgmt&portname=sendip portname: net/link-monitor-applet broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=link-monitor-applet portname: net/rmsg broken because: Does not build after the removal of utmp(5) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=rmsg portname: net/slirp broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=slirp portname: science/afni broken because: R_io.so fails to build with R-3.0.2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=science&portname=afni portname: security/pam_alreadyloggedin broken because: Does not build with utmpx. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pam_alreadyloggedin portname: sysutils/hyperic-sigar broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=hyperic-sigar portname: sysutils/p5-Sys-Utmp broken because: fails to build with new utmpx build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=p5-Sys-Utmp portname: textproc/libextractor broken because: does not package build errors: http://beefy2.isc.freebsd.org/bulk/10amd64-default/latest/logs/errors/libextractor-0.6.2_15.log ((not currently populated)) overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=libextractor portname: x11/gnome-shell broken because: Doesn't build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=gnome-shell