From owner-freebsd-mono@freebsd.org Thu Nov 23 21:01:18 2017 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 88FA2DF58B0 for ; Thu, 23 Nov 2017 21:01:18 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-wm0-x22c.google.com (mail-wm0-x22c.google.com [IPv6:2a00:1450:400c:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 207E27A31D for ; Thu, 23 Nov 2017 21:01:18 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: by mail-wm0-x22c.google.com with SMTP id x63so18965050wmf.2 for ; Thu, 23 Nov 2017 13:01:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version; bh=O4djN7xy/zuuuOoRrKSYzuKs4CfbstQJkgg11NaF9ek=; b=tf802fpwPJwToVdZqFStkaS9jfYWMzYEi0LH8HtmO5minr9M4ZFGDRjBC5uDlfUOb8 1Kc0C7t3sTY1q6n/3LXJ59RPuRzpFuBLcB5HM/EawMT7nkWlDVhLhK3kcq7ZbeU9dSSt eKrnsVNH1sv5T/ciS5tHPa/t2v80lNwT75fVWVMndZKghMD6A9qRf46KblwkKTVd2IHq HOTa2qqO2wiNBSPaqmTcL1CZjR//Ei/b0SCAgJ2OOtXy9VmOEgQOTFVnoVTzjIEqcDPX SDeuztKM7uWBs01ohzYQGBXzDv/zBhKyPUU2tObb97E978SPAMkBi4L6y4grscRx4fkw gWeQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version; bh=O4djN7xy/zuuuOoRrKSYzuKs4CfbstQJkgg11NaF9ek=; b=SnrPuBFji4hp25hSKWeaLit2isFNWoMkVzNqq2XsEwt4T0hrLYx3LJHA2yNRU1WQib ZFdE08rvBJY+1dV54rsEonHltfgxmjTFystdCujQ3SYJk9XJiHLaWO9MF8Pji+d1lFHp Pcbjltf9YZAhLRa+daqLkWpwrCUSeQ5HzxAN/SdSLzRmUglgQpRN6BLPa+5U2/811NlS bFUxcJvYdF/0ScEPdYzBohtaRbiOv/nXWFNPBG4fABWDeI9PoJdkZ4FTzH0xx17EAxF/ pq/+z7iz5OU7n9a+vSxzqYg4PDnP6LNn1m2pbMipMQFF4f9cuvS6QX9UBHFD22TCWB2F 6uaA== X-Gm-Message-State: AJaThX7BFAZY/1nBxHB31jNjO0zbwWh3HENLFrxO8fcq1A1KRq/mUNTh /0HAAAkV5Dzk49RkMqUN+qEvBpYG X-Google-Smtp-Source: AGs4zMal2qryPO6N+jK9tfX1zXzPH5flQffSWY6lIBZrhfg2hVUJOTrlWwvfNZ1XYeRScc5qen1kCA== X-Received: by 10.28.206.8 with SMTP id e8mr7515236wmg.80.1511470875675; Thu, 23 Nov 2017 13:01:15 -0800 (PST) Received: from dragon.local (8ta-228-198-134.telkomadsl.co.za. [197.228.198.134]) by smtp.googlemail.com with ESMTPSA id y2sm4849052wra.18.2017.11.23.13.01.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 23 Nov 2017 13:01:14 -0800 (PST) From: David Naylor To: Freebsd-mono Subject: Re: Update on porting mono 5 Date: Thu, 23 Nov 2017 23:01:11 +0200 Message-ID: <1794151.yOGvER6fHk@dragon.local> Organization: Private User-Agent: KMail/4.14.10 (FreeBSD/11.1-RELEASE-p1; KDE/4.14.30; amd64; ; ) In-Reply-To: <1723656.WBGSMfOCjc@dragon.local> References: <17078253.u2dgjZK1Z6@dragon.local> <1723656.WBGSMfOCjc@dragon.local> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3018092.7dlldgPgbx"; micalg="pgp-sha512"; protocol="application/pgp-signature" X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Nov 2017 21:01:18 -0000 --nextPart3018092.7dlldgPgbx Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" On Monday, 13 November 2017 23:11:03 David Naylor wrote: > In the interim, I tried my hand at my own exp-run [1][2][3]. And things > didn't go well (well the exp-run was a success, but the results...). > > It appears that somehow the assemblies are being delay signed during build, > instead of signed. It appears csc(1) [the replacement for mcs(1)] does not > support signing on non-Windows machines [4]. Mono recommends sn(1) should > be used to sign the dll after build. I suggest we patch > Microsoft.Common.CurrentVersion.target to restore signing functionality. I've fixed signing of assemblies by using sn(1) after the compile step in the CoreCompile target. This fixed one port and pushed post packages to breaking due to changes from mdb to pdb debug info. > Any help with the above or the following will be most appreciated: > - Bumping the PORTREVISION of all ports that depend on mono > - Patching security/ca_root_nss to update/sync/clear the mono certificate > (see cet-sync(1)) > - (Optional) Patch mono to store the certificates in $PREFIX, instead of > /usr/local/ - fix the follow port's pkg-plist: - devel/dbus-sharp - devel/mono-addins - devel/newtonsoft-json - multimedia/emby-server - investigate why the following ports do not build: - games/openra - security/gnome-keyring-sharp --nextPart3018092.7dlldgPgbx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQKTBAABCgB9FiEElI7FEaJ/AwLnmbU6rWP6jday2lUFAloXNxdfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDk0 OEVDNTExQTI3RjAzMDJFNzk5QjUzQUFENjNGQThERDZCMkRBNTUACgkQrWP6jday 2lWBWg//eD02Go/vhxzEfNsklUhB00dCD/mRHZvvPzQmd8bvT5rxM+c/zIvY7Cvl zy8vTXaANx0cq6DAPM8yRYfngz/cmlCeU9H7TzWCZ5NvlHPKIXjTOSZ6MaKhQ99N jghrRr1Bv6aX3iHr6zG58H1yxp9ri5nBn5adzGX6OjYNISlBKPtYgVSWSJUFX8mB h7K0r0HVaNZ/ippd0lc7X7CFDi4W7pEi7gPD42DPIdciaLGn+cxHcoDuTjP34HAs 3+muzO59E4gzuJ/JIdnx0xLQ61Y/8UzkoXxo6pWkEOhtKNj4NOJq81ho5Z9zvHFX bomXkng2AjGnvr9szwiFQGPVCZrlTEhCcqLpdYCJWqm+gN9K0XNegNBFibRjbBDj XH3b1YQCyKjpJw++OvRbMQ1efTfcp2KaV1kEHqS24KHkCdxEI4tsF77pKGMAfcSL okC1p8+1TBvIRvktJxI4/8YLl3evfRWuv9Mq48ubj+KFNrsoAhIxFYbOxKdqSO2d Gqravp14WEcEtsIouhPLaGqXbtCTmztIuiAOnv3pg9vCG5c4kpmtu2BFnABzxFIC b4hiy0Wh1I5vWSsq+ZlppuuIzYzfBOpLpP8Z1pPkcU1O0E8OFAIdG1p+n1Qcc4qP mUvF27pObl86lXZB/rnkjuH47v3Ra6m05WCVbwolgqf/urqWQqA= =1RnU -----END PGP SIGNATURE----- --nextPart3018092.7dlldgPgbx-- From owner-freebsd-mono@freebsd.org Fri Nov 24 05:33:33 2017 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68E2EDBA48D for ; Fri, 24 Nov 2017 05:33:33 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E131E669A1 for ; Fri, 24 Nov 2017 05:33:32 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x236.google.com with SMTP id c188so16620295lfd.5 for ; Thu, 23 Nov 2017 21:33:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QOKaTJw9B5t3ojVf2lmrn9BrO1v/jijlKC4TBV8jmwk=; b=GquK3ApShyMJo0GRZ/aIAEyyNVcY0ILfw+fZf0goTtg8hC21fVnjwJA1Qeet8vEvPr xFEo62tsEc8DTtOCwmjHz77EgwtJa91OzTANQwHpBLQmT1HCuyOsxIgBXrXPIWIVrSPR K+FKNs5xPijLMb5MDqFbyjf6FlzZXHzUMagXiM0rhF2Rpo4IlSuRD/ijOdrQeIlvJixW LBpMCrW53j0TpCPNrjvBTG72iJWUR94sTmIk6zNcgH76THVIKRRNdXLdP7TGV1Q007w2 7pcese0fpxRiwifu5XgKUrV0i7G01cuH6E4q3AjSAswzK18T6ONAjhwqiNqjY7qTnmnH kYuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=QOKaTJw9B5t3ojVf2lmrn9BrO1v/jijlKC4TBV8jmwk=; b=J6Stito74dFOkLlLbinxbcCYAKndrFWEEsfAn+VEdi9gyII04sXX/IJYuaMu5qtnTW R1+otrYIRkVhbrDixH+yg6F+mRoaDLFTbTojxBr4wJdV/S1g5tgvPWzEwOTnzvBx9Ty6 OqbmIaMp9DIZ1VdwMzDL2f3T3zhKucyoI+YLG+Tw0WWUQjo+fJ9OnDlcqaQLeUTZ1rYd JZ5KaJ9VrI4Sd93cgiBW7HRXV2aRuv+5lYymQK2uZ9Fo4r+q20eE5Rt7ByTox9QgiIJ5 2yNF+fug5SM1wwUJoXlCmGrvXMV6wFNQw12GIYbj7lzYY0wjZG/J2DtibLJAEnk96lSh Uc6A== X-Gm-Message-State: AJaThX4FZHaL9qyPls46u5/KRGG8Bl6fdR6kXvXYaXEemUxYPuVjc52R imEGdyNsmnJ3tj4CY9TT0e0JQZkyaEs6RQ7snxI= X-Google-Smtp-Source: AGs4zMaHK8ZpkOETtJ0E10kQaPwuybc/hbpcEaQhdxn0wo35cry7LQMKIL9ke1yBpclhIH0Kqhm3ofAZMQ1AMSEPkXs= X-Received: by 10.46.91.79 with SMTP id p76mr10635533ljb.22.1511501610686; Thu, 23 Nov 2017 21:33:30 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.14.1 with HTTP; Thu, 23 Nov 2017 21:33:29 -0800 (PST) In-Reply-To: <1794151.yOGvER6fHk@dragon.local> References: <17078253.u2dgjZK1Z6@dragon.local> <1723656.WBGSMfOCjc@dragon.local> <1794151.yOGvER6fHk@dragon.local> From: Russell Haley Date: Thu, 23 Nov 2017 21:33:29 -0800 Message-ID: Subject: Re: Update on porting mono 5 To: David Naylor Cc: Freebsd-mono , Tomas Weinfurt Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 05:33:33 -0000 On Thu, Nov 23, 2017 at 1:01 PM, David Naylor wrote: > On Monday, 13 November 2017 23:11:03 David Naylor wrote: >> In the interim, I tried my hand at my own exp-run [1][2][3]. And things >> didn't go well (well the exp-run was a success, but the results...). >> >> It appears that somehow the assemblies are being delay signed during build, >> instead of signed. It appears csc(1) [the replacement for mcs(1)] does not >> support signing on non-Windows machines [4]. Mono recommends sn(1) should >> be used to sign the dll after build. I suggest we patch >> Microsoft.Common.CurrentVersion.target to restore signing functionality. > > I've fixed signing of assemblies by using sn(1) after the compile step in the > CoreCompile target. This fixed one port and pushed post packages to breaking > due to changes from mdb to pdb debug info. Wow. I haven't seen sn or SigningTool in a long time. Nice job. I didn't even think of it. >> Any help with the above or the following will be most appreciated: >> - Bumping the PORTREVISION of all ports that depend on mono >> - Patching security/ca_root_nss to update/sync/clear the mono certificate >> (see cet-sync(1)) >> - (Optional) Patch mono to store the certificates in $PREFIX, instead of >> /usr/local/ > - fix the follow port's pkg-plist: > - devel/dbus-sharp > - devel/mono-addins > - devel/newtonsoft-json > - multimedia/emby-server > - investigate why the following ports do not build: > - games/openra > - security/gnome-keyring-sharp I'm perusing your review right now. I haven't absorbed enough to comment yet. You seem to have added a new make variable for nuget_depends. Can you speak a little about that? I am wondering if leverage that in dotnet core to pull in the managed assemblies that we can't build on FreeBSD? Russ From owner-freebsd-mono@freebsd.org Fri Nov 24 06:58:18 2017 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6EE1ADBB4DE for ; Fri, 24 Nov 2017 06:58:18 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E5D1E68372 for ; Fri, 24 Nov 2017 06:58:17 +0000 (UTC) (envelope-from russ.haley@gmail.com) Received: by mail-lf0-x22f.google.com with SMTP id c188so16796320lfd.5 for ; Thu, 23 Nov 2017 22:58:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=kvVbmaQMII/8m3au6VSuaPl0j//8vYRVqHxj+xDWHck=; b=Mhv2iBFocLtpqGOg75hD1hGssvtdNaAB8BdZ341W8lquIPZ/lMQTNp5W86+PZrN8HS naN4zuqXL+BJEwygjpC3wxfsZqqCAD22d2c72yfxc6khkhOKjJFKAbt2jiAJKVuGk5SH Ewi/2wOhtlEysWQkoEDDRTjXwiMp1ds+eK8cSXD9eKjWAXU6ApnGWwxXVoD89NTQ207B P8SoAjkHTsBep59lrnvKftsnbrRl4yME0peLMyH7ru4lXB866tjIzhfECSgn/c+yKCAY INIJoxkkSEGkFC1cK7hcaw1Eyz+lAKLb3BP/amulNLTW6rTOh95NHrZ7gb4vWqkngQ/9 QgFg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kvVbmaQMII/8m3au6VSuaPl0j//8vYRVqHxj+xDWHck=; b=P6Go8ineElIUoNHnXxcc+ce4VD4ZX12mF8Nh2P/EuyNrYv9+S7DplOomIegJr4Vn+Y 1MMVhRN38ZcxeFWB7r2xngiscwTHOfMJ5TF6ELTVxlzTAOMqyMJDysHNeRQOxVnuyfoV JlpHsZ44eAcooiv6HZWed+KpoJg2cgq8rrupQX6bSzth5KuyQamFxSEk2nyYyxcF0Hzc ievsQF8nzXh4QVbh/GfkwidcfIQAnaqi55ZgYIszSSDO/KXD7BUXg/zdv+9GXHEjBY7C ZPGlbYBfIXfrkv0lOA4jzQ5V3qri6LoCjj4UIp4zp3Whqf0lMinsSwdXdASeuxjBFEuc 9yVw== X-Gm-Message-State: AJaThX7HKshjfOwVt7zSOHv/8B0lTvXIDylmIoaUkQoPsp6eMa6MAW0Y PDh38xje4lT6xw6VQqhQ+L40Nb1uN9xJTDrguFM= X-Google-Smtp-Source: AGs4zMaVgVSflD+ErfFVe+sQu4lkPZYcQlCb1yOGhEjM+D+mQqpNWPC481uHFZ5a2kEXqPCiUNA5+Fk5cJnqiZSDm3A= X-Received: by 10.25.232.17 with SMTP id f17mr9074446lfh.54.1511506696014; Thu, 23 Nov 2017 22:58:16 -0800 (PST) MIME-Version: 1.0 Received: by 10.46.14.1 with HTTP; Thu, 23 Nov 2017 22:58:15 -0800 (PST) In-Reply-To: References: <17078253.u2dgjZK1Z6@dragon.local> <1723656.WBGSMfOCjc@dragon.local> <1794151.yOGvER6fHk@dragon.local> From: Russell Haley Date: Thu, 23 Nov 2017 22:58:15 -0800 Message-ID: Subject: Re: Update on porting mono 5 To: David Naylor Cc: Freebsd-mono , Tomas Weinfurt Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Nov 2017 06:58:18 -0000 On Thu, Nov 23, 2017 at 9:33 PM, Russell Haley wrote: > On Thu, Nov 23, 2017 at 1:01 PM, David Naylor wrote: >> On Monday, 13 November 2017 23:11:03 David Naylor wrote: >>> In the interim, I tried my hand at my own exp-run [1][2][3]. And things >>> didn't go well (well the exp-run was a success, but the results...). >>> >>> It appears that somehow the assemblies are being delay signed during build, >>> instead of signed. It appears csc(1) [the replacement for mcs(1)] does not >>> support signing on non-Windows machines [4]. Mono recommends sn(1) should >>> be used to sign the dll after build. I suggest we patch >>> Microsoft.Common.CurrentVersion.target to restore signing functionality. >> >> I've fixed signing of assemblies by using sn(1) after the compile step in the >> CoreCompile target. This fixed one port and pushed post packages to breaking >> due to changes from mdb to pdb debug info. > Wow. I haven't seen sn or SigningTool in a long time. Nice job. I > didn't even think of it. > >>> Any help with the above or the following will be most appreciated: >>> - Bumping the PORTREVISION of all ports that depend on mono >>> - Patching security/ca_root_nss to update/sync/clear the mono certificate >>> (see cet-sync(1)) >>> - (Optional) Patch mono to store the certificates in $PREFIX, instead of >>> /usr/local/ >> - fix the follow port's pkg-plist: >> - devel/dbus-sharp >> - devel/mono-addins >> - devel/newtonsoft-json >> - multimedia/emby-server >> - investigate why the following ports do not build: >> - games/openra >> - security/gnome-keyring-sharp > > I'm perusing your review right now. I haven't absorbed enough to > comment yet. You seem to have added a new make variable for > nuget_depends. Can you speak a little about that? I am wondering if > leverage that in dotnet core to pull in the managed assemblies that we > can't build on FreeBSD? > > Russ I submitted some comments on the patch. You've put in quite a bit of work! It seem that you are pulling binaries for Nuget, Rosyln and a big chunk of the dotnet framework. I can't help but think we could directly use this port as a framework to build the managed assemblies for core2 if we have all that working in order to build mono. I also see nuget3000 and paket are used. Can you describe where these are needed and what they are used for? I could have asked this on the review but thought this is a better for others on the list that don't want to wade through a review. :) Night, Russ