From owner-freebsd-ports@FreeBSD.ORG Fri Feb 7 08:28:07 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 1749E37B for ; Fri, 7 Feb 2014 08:28:07 +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 0410B1FE7 for ; Fri, 7 Feb 2014 08:28:07 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.7/8.14.7) with ESMTP id s178S6e9071373 for ; Fri, 7 Feb 2014 08:28:06 GMT (envelope-from linimon@FreeBSD.org) Date: Fri, 7 Feb 2014 08:28:06 GMT Message-Id: <201402070828.s178S6e9071373@portsmon.freebsd.org> From: linimon@FreeBSD.org To: ports@freebsd.org Subject: FreeBSD unmaintained 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 Feb 2014 08:28:07 -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: biology/fasta3 broken because: Invalid checksum, seems like the software was rerolled build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=fasta3 portname: biology/finchtv broken because: fails to checksum build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=biology&portname=finchtv 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/msql broken because: Broken on FreeBSD 9+ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql portname: graphics/k3d broken because: Fails to configure build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=k3d 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: multimedia/gxine broken because: Does not build with recent libxul build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=gxine 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/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: 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: www/ump broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=ump portname: x11-wm/stumpwm 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=x11-wm&portname=stumpwm