From owner-freebsd-mono@FreeBSD.ORG Mon Oct 17 11:08:16 2011 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7F5CC106566B for ; Mon, 17 Oct 2011 11:08:16 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 55B968FC1E for ; Mon, 17 Oct 2011 11:08:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p9HB8Gl6000285 for ; Mon, 17 Oct 2011 11:08:16 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p9HB8FrH000283 for mono@FreeBSD.org; Mon, 17 Oct 2011 11:08:15 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 17 Oct 2011 11:08:15 GMT Message-Id: <201110171108.p9HB8FrH000283@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: mono@FreeBSD.org Cc: Subject: Current problem reports assigned to mono@FreeBSD.org X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Oct 2011 11:08:16 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- a ports/144224 mono [PATCH] lang/mono Fix build with new GCC 1 problem total. From owner-freebsd-mono@FreeBSD.ORG Fri Oct 21 06:28:31 2011 Return-Path: Delivered-To: mono@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8DC1B1065677 for ; Fri, 21 Oct 2011 06:28:31 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from koala.droso.net (koala.droso.net [IPv6:2001:6c8:130:400::6]) by mx1.freebsd.org (Postfix) with ESMTP id 3C43B8FC0C for ; Fri, 21 Oct 2011 06:28:31 +0000 (UTC) Received: from koala.droso.net (localhost.droso.net [127.0.0.1]) by koala.droso.net (8.14.4/8.14.4) with ESMTP id p9L6SU1n039775 for ; Fri, 21 Oct 2011 08:28:30 +0200 (CEST) (envelope-from linimon@FreeBSD.org) Date: Fri, 21 Oct 2011 08:28:30 +0200 (CEST) Message-Id: <201110210628.p9L6SU1n039775@koala.droso.net> From: linimon@FreeBSD.org To: mono@FreeBSD.org Cc: Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: portmgr-feedback@FreeBSD.org List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Oct 2011 06:28:31 -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 6.x/7.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/muine broken because: does not compile build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110921072835/muine-0.8.11_7.log (_Sep_24_03:38:30_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=muine portname: irc/smuxi broken because: Does not build build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=smuxi portname: lang/boo broken because: does not build build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.9.20110921072835/boo-0.9.4.9.log (_Sep_24_04:43:14_UTC_2011) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=boo portname: multimedia/moonlight broken because: Basically does not work build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=moonlight 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.