From owner-freebsd-gnome@FreeBSD.ORG Sun Jul 7 08:28:12 2013 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BC5A4EC1 for ; Sun, 7 Jul 2013 08:28:12 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from portsmon.freebsd.org (portsmon.freebsd.org [IPv6:2001:1900:2254:206a::50:3]) by mx1.freebsd.org (Postfix) with ESMTP id 985B319A7 for ; Sun, 7 Jul 2013 08:28:12 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.7/8.14.7) with ESMTP id r678SCdq002766 for ; Sun, 7 Jul 2013 08:28:12 GMT (envelope-from linimon@FreeBSD.org) Date: Sun, 7 Jul 2013 08:28:12 GMT Message-Id: <201307070828.r678SCdq002766@portsmon.freebsd.org> From: linimon@FreeBSD.org To: gnome@freebsd.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Jul 2013 08:28:12 -0000 Dear FreeBSD port maintainer: 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: graphics/py-clutter broken because: bad plist build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=py-clutter portname: net/libproxy-mozjs broken because: Does not work with newer libxul build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=libproxy-mozjs portname: net/opal broken because: does not compile on 9.X build errors: http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.8.20130510010703.pointyhat/opal-2.2.11_7.log (May 13 14:34:01 UTC 2013) overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=opal portname: x11/gnome-shell broken because: Doesn't build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=gnome-shell 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 , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD.