From owner-freebsd-gnome@FreeBSD.ORG Sat Jan 10 12:56:45 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 20FCF16A4CE for ; Sat, 10 Jan 2004 12:56:45 -0800 (PST) Received: from ms-smtp-01-eri0.texas.rr.com (ms-smtp-01.texas.rr.com [24.93.47.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id F270743D39 for ; Sat, 10 Jan 2004 12:56:42 -0800 (PST) (envelope-from linimon@FreeBSD.org) Received: from bento.lonesome.com (cs242719-195.austin.rr.com [24.27.19.195]) i0AKuf4a014408 for ; Sat, 10 Jan 2004 14:56:41 -0600 (CST) Date: Sat, 10 Jan 2004 14:56:41 -0600 (CST) Message-Id: <200401102056.i0AKuf4a014408@ms-smtp-01-eri0.texas.rr.com> From: linimon@FreeBSD.org To: gnome@FreeBSD.org X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Jan 2004 20:56:45 -0000 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 by the Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that the latest -CURRENT includes gcc3.3, 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 ore more build environments that you do not have access to, please ask for help on the freebsd-ports mailing list. The build 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 or 5.x, with target architecture'.) portname: lang/mono build errors: ??? arch (Oct 3 01:50:01 GMT 2003) If these build 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 build errors 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 build 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.