From owner-freebsd-mono@FreeBSD.ORG Sun Sep 21 08:28:12 2014 Return-Path: Delivered-To: mono@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5EC033E9 for ; Sun, 21 Sep 2014 08:28:12 +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)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 368B8BE7 for ; Sun, 21 Sep 2014 08:28:12 +0000 (UTC) Received: from portsmon.freebsd.org ([127.0.1.104]) by portsmon.freebsd.org (8.14.9/8.14.9) with ESMTP id s8L8SCgM011593 for ; Sun, 21 Sep 2014 08:28:12 GMT (envelope-from linimon@FreeBSD.org) Date: Sun, 21 Sep 2014 08:28:12 GMT Message-Id: <201409210828.s8L8SCgM011593@portsmon.freebsd.org> From: linimon@FreeBSD.org To: mono@freebsd.org Reply-To: portmgr-feedback@FreeBSD.org Subject: FreeBSD ports that you maintain which are currently marked broken X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2014 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: devel/monodevelop-database broken because: Fails to build with monodevelop-5.0.1 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=monodevelop-database 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. From owner-freebsd-mono@FreeBSD.ORG Tue Sep 23 22:56:52 2014 Return-Path: Delivered-To: freebsd-mono@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 8A7DDFE2 for ; Tue, 23 Sep 2014 22:56:52 +0000 (UTC) Received: from marvin.blogreen.org (marvin.blogreen.org [IPv6:2001:470:1f13:b9c::2]) by mx1.freebsd.org (Postfix) with ESMTP id 3DA097D9 for ; Tue, 23 Sep 2014 22:56:52 +0000 (UTC) Received: by marvin.blogreen.org (Postfix, from userid 1001) id 6475D18F71A; Wed, 24 Sep 2014 00:56:44 +0200 (CEST) Date: Wed, 24 Sep 2014 00:56:44 +0200 From: Romain =?iso-8859-1?Q?Tarti=E8re?= To: Ben Woods Subject: Re: Mono expecting /proc/net/route Message-ID: <20140923225644.GA73505@FreeBSD.org> Mail-Followup-To: Ben Woods , freebsd-mono@freebsd.org References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pf9I7BMVVzbSWLtt" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://romain.blogreen.org/pubkey.asc User-Agent: Mutt/1.5.23 (2014-03-12) Cc: freebsd-mono@freebsd.org X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 22:56:52 -0000 --pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi On Fri, Sep 19, 2014 at 11:03:27PM +0800, Ben Woods wrote: > In the process of trying to get http://mediabrowser.tv/ to work on FreeBS= D, > I have come across a bug in the port of mono to FreeBSD where it expects = to > be able to use /proc/net/route to find the IP address of the computer. >=20 > Reviewing the mono code it appears it expects a few other things from /pr= oc > which don't exist in FreeBSD, even with linprocfs (e.g. /proc/net/snmp). > https://github.com/mono/mono/search?utf8=3D%E2%9C%93&q=3D%22proc%2Fnet%22= &type=3DCode >=20 > Any ideas about the best way to resolve this? >=20 > More details with my specific issues relating to MediaBrowser can be found > here: > http://mediabrowser.tv/community/index.php?/topic/2636-mb3-on-freenas-plu= gin/page-4 Are you refering to this? https://github.com/mono/mono/blob/effa4c07ba850bedbe1ff54b2a5df281c058ebcb/= mcs/class/System/System.Net.NetworkInformation/IPInterfaceProperties.cs#L77 AFAICR, the information should be available from a sysctl (what netstat(8) does) or from a PF_ROUTE socket (what route(8) does), but it may be easier to parse the output of netstat(8) instead of reimplementing parts of netstat(8) or route(8) in managed code=E2=80=A6 If you have a patch, feel free to share it here so that I can include it ;-) --=20 Romain Tarti=C3=A8re http://people.FreeBSD.org/~romai= n/ pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciated) --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGcBAEBAgAGBQJUIfqsAAoJELpNHZVREjNv40kL/2zbZYp8CuLBk+sEhZQsckEj rriMhVoQSBaxxyQRF3slMh3BjUPGwC0lZFeytMrd8Za7mYA0EGVJnlzsA6AcCI/a EN+/UGBuoqtVMg9Y+Wf657x9lWqcqoT8rsVUoGPr2DrsEiHFJoJvwT5VkYOll4Tc ZGI2i7poFjBJ3XTi1A7qk5rUDeLk4YwKUVJw3tzQdYxDXPXpNNS5jdC8/d/K7N3F lm3gf5kXNhiVpcp5Xa9G5rOSvBSTXgtgFXfQ4V9MxPplMVaSt1YtzypCka1TTawx EJ94WIHz/euFwUl4hbvfft6h14hpWYIVwclfG8s7lK/tr2RkrBR6ABY6rktppU4V cvNgw1DpXM0y6oF0xCn75uhusQM+7ba4nsfZSfFwRbBenWw5G32orA8S+K+hAs5l 7y57OLBJFo5doaj0SdOgg/ZkkXQqZA0cj70wD0objiT+TCWBz+6G0ciA+AvyqJFS hnIoxkVib8/VTn4M3eAybqWH9hIGxjnsGH8j8st14Q== =Ehtn -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt-- From owner-freebsd-mono@FreeBSD.ORG Tue Sep 23 23:02:38 2014 Return-Path: Delivered-To: freebsd-mono@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 6CB0D302 for ; Tue, 23 Sep 2014 23:02:38 +0000 (UTC) Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 06C8D8B0 for ; Tue, 23 Sep 2014 23:02:37 +0000 (UTC) Received: by mail-wg0-f47.google.com with SMTP id y10so5490394wgg.6 for ; Tue, 23 Sep 2014 16:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=pRJcrLxHrVg9XSAypaSMh86o32Ja0jLFUWVvBeBzXlE=; b=hwYGtHp/sUbRKak4sWMY5Jrs1PizU5luzKG64ozZIX69lthBDNUYdMglZdMZXKStaP W74ymx6ZYy3Qyod0vhGBKpSn+VBenn7Gsy7KHne9Tqh459z+wmOY8Lyky+7i7c9QoTvN ZTSuqJTyAy7X7ysENKvAsa0eI1F34BGHl9E8eHeMfHcb7t4r5tw2x5hPV6uaNCHJfaFl 79uMpKAm9z1EBIefncXZIwdCl4PRcCT4PO9LSfuC9LWRAG/8Gk2cUhSqs09hgvND5fCX ZHR3GobpwC+Zl0iwfh8AW0FFUJOD5QCkevtDk2GBoNMhgDH3EqBEpw01e4KBa/flnGXR uPZQ== MIME-Version: 1.0 X-Received: by 10.194.120.101 with SMTP id lb5mr3227531wjb.84.1411513355995; Tue, 23 Sep 2014 16:02:35 -0700 (PDT) Received: by 10.194.190.78 with HTTP; Tue, 23 Sep 2014 16:02:35 -0700 (PDT) In-Reply-To: <20140923225644.GA73505@FreeBSD.org> References: <20140923225644.GA73505@FreeBSD.org> Date: Wed, 24 Sep 2014 07:02:35 +0800 Message-ID: Subject: Re: Mono expecting /proc/net/route From: Ben Woods To: "freebsd-mono@freebsd.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Sep 2014 23:02:38 -0000 Yes, that's what my specific problem was. I will see if I can generate a patch... I'm just wondering what it would look like if it was adopted into the upstream code (There is a separate set of functions for Mac IP addressing, should there be a separate set of BSD functions?). On Wednesday, September 24, 2014, Romain Tarti=C3=A8re wrote: > Are you refering to this? > > https://github.com/mono/mono/blob/effa4c07ba850bedbe1ff54b2a5df281c058ebc= b/mcs/class/System/System.Net.NetworkInformation/IPInterfaceProperties.cs#L= 77 > > AFAICR, the information should be available from a sysctl (what > netstat(8) does) or from a PF_ROUTE socket (what route(8) does), but it > may be easier to parse the output of netstat(8) instead of > reimplementing parts of netstat(8) or route(8) in managed code=E2=80=A6 > > If you have a patch, feel free to share it here so that I can include it > ;-) > > > -- > Romain Tarti=C3=A8re http://people.FreeBSD.org/~rom= ain/ > pgp: 8234 9A78 E7C0 B807 0B59 80FF BA4D 1D95 5112 336F (ID: 0x5112336F) > (plain text =3Dnon-HTML=3D PGP/GPG encrypted/signed e-mail much appreciat= ed) > --=20 -- From: Benjamin Woods woodsb02@gmail.com