From owner-freebsd-mono@freebsd.org Wed Oct 24 22:10:54 2018 Return-Path: Delivered-To: freebsd-mono@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 53D0F10719A6 for ; Wed, 24 Oct 2018 22:10:54 +0000 (UTC) (envelope-from clhamilto@gmail.com) Received: from mail-vk1-xa2c.google.com (mail-vk1-xa2c.google.com [IPv6:2607:f8b0:4864:20::a2c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E7B557C1DE; Wed, 24 Oct 2018 22:10:53 +0000 (UTC) (envelope-from clhamilto@gmail.com) Received: by mail-vk1-xa2c.google.com with SMTP id 22so846205vkz.11; Wed, 24 Oct 2018 15:10:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=pdzHl2LX/mreZ0yqkyLWMPukI2UzG1WdYtVQ0GGROKw=; b=mxubCMZHiqijBiAE+LC4Z1Kc7dYIoocWtI7v+NrAjAnjzKQnHd0yPKnS0Vspl1Aj3E BavORj03InQFPwRY3AJ/TAQgqRiXtkKUa0lP60/cHnlDMkglE+cY8IaVKBxycoKXeVMb Xbl/Z2BRAeuHwg2QP8ZNqLLYEIz8t6ySxYPJzrPpxE4pQ0a71hmPVyMkk8JpJj8+a2WR 0ooY+WHaioCrpf9ePiIZnhoFnB7rO5DNxykw8FRalUjGji/WspecBkRxLfoxLODJkIUy /KgGCtIuC7vVMEQpkLuAd89arpMHun4kYVUp6ec8SQryH6AFkawT2QpGBUKapI3EhtXC chfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=pdzHl2LX/mreZ0yqkyLWMPukI2UzG1WdYtVQ0GGROKw=; b=PpcXC5be6CBeezGOnOr0oVlOJKU1ffl8MHVq1/vBY7vH5o0iNeQKwS7cQfvEGKNxEu es6XQaWPktDJQf/uKWuNkJiLD9cvKaQfSF5s/jusSq+0LZ4dAHjW14a8OumzwFfP5yjg dnHMiywiC/uLWLIwitFBGs4AYMehP57VENZLKGBIIsO7QxjXtVoTCgtUHHVEBgNC51KD istM8L9Zrjo1ADf+7Oqy/1rcZv0Mb9ZCsIBKE4Nwo+xjT2iStADNUG5fyxO98OahPgHn Oqw5LgHzNixo4wE/0JNJPx9E0yA61mfRJfaZSbkUp7Q3GLguoX8sN5Y/HGXpc86Wowdy iHAw== X-Gm-Message-State: AGRZ1gL4X36S1vLN6qIevSgslwfpMkcX++OHI1IJFWouVG9S38mjzd1k iGfLVeffORBRCf14y4W26k1pVLwN X-Google-Smtp-Source: AJdET5ceJeWkV4qo0qfKnB8gFRC4LcWaLyS9DPdMdKmF7N07mIMjsFsooaZFSLQoeXtSnZkSDVQdLg== X-Received: by 2002:a1f:4883:: with SMTP id v125-v6mr2088589vka.18.1540419053101; Wed, 24 Oct 2018 15:10:53 -0700 (PDT) Received: from lenoil8.lenoil.net (c-76-106-45-221.hsd1.va.comcast.net. [76.106.45.221]) by smtp.gmail.com with ESMTPSA id z7-v6sm1352142vkd.2.2018.10.24.15.10.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 24 Oct 2018 15:10:52 -0700 (PDT) Subject: Re: Mono on PowerPC64 To: freebsd-mono@freebsd.org, Justin Hibbits References: <7d94a36e-76f5-44a0-ebea-4f4f9f102677@gmail.com> <20181011094641.6c9b270c@ralga.knownspace> From: Curtis Hamilton Message-ID: Date: Wed, 24 Oct 2018 18:10:51 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD powerpc; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20181011094641.6c9b270c@ralga.knownspace> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-mono@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Mono and C# applications on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Oct 2018 22:10:54 -0000 All, I've been successful in building Mono 5.x for powerpc64. I currently have Mono 5.14.0.177 running. However, there are some remaining issues. - VisualC# (csc.exe) does not support big endian and probably never will. - Mono for powerpc64 SIGABRT when building or running F#. On Powerpc, you can build F#, by changing the value for Tailcall" in cpu-ppc.md from 120 to 124. You can work around the VisualC# issue by substituting mcs.exe for csc.exe. However, there's not currently a fix or work around for F# on powerpc64. I've also been able to build most other .NET tools and bindings. I was able to build MonoDevelop 6.1.2 on both 32-bit and 64-bit powerpc, with a little editing of the solution file "Main.sln", removing all references to FSharp. This gives me a working development environment, minus the F# binding. There are issues with compiling new versions of MonoDevelop which I will address in another forum. Fixes for mono on powerpc/powerpc64 have already been submitted and committed to the mono project source master on GITHUB. However, previously released versions require port patches which I'll submitt via PR. I can provide additional information if anyone is interested. - Curtis On 10/11/18 10:46, Justin Hibbits wrote: > Hi Curtis, > > At the time I did the ppc32 port I did not have a ppc64 machine, then I > lost interest. It was mostly a checkbox for m, and every app I tried > written in C# was very unstable, so I didn't pursue it any further than > that. As you saw, it bitrotted pretty quickly. > > What issues are you running into with 64-bit? > > - Justin > > On Wed, 10 Oct 2018 17:41:17 -0400 > Curtis Hamilton wrote: > >> Justin, >> >> I understand that you once worked on Mono for ppc/ppc64. If so, were >> you able to get it working on ppc64? >> >> With the recent changes in Mono 5.x, I got 32-bit Mono working. But >> have run into a brick wall with 64-bit. >> >> Regards, >> >> Curtis >> >> >> >> -------- Forwarded Message -------- >> Subject: freebsd-mono Digest, Vol 366, Issue 3 >> Date: Wed, 10 Oct 2018 12:00:01 +0000 >> From: freebsd-mono-request@freebsd.org >> Reply-To: freebsd-mono@freebsd.org >> To: freebsd-mono@freebsd.org >> >> >> >> Send freebsd-mono mailing list submissions to >> freebsd-mono@freebsd.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.freebsd.org/mailman/listinfo/freebsd-mono >> or, via email, send a message with subject or body 'help' to >> freebsd-mono-request@freebsd.org >> >> You can reach the person managing the list at >> freebsd-mono-owner@freebsd.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of freebsd-mono digest..." >> >> >> Today's Topics: >> >> 1. Re: Mono on PowerPC64 (Mark Felder) >> 2. [Bug 232060] lang/mono: Fix for Mono build on FreeBSD PowerPC >> (bugzilla-noreply@freebsd.org) >> 3. Re: Mono Build on PowerPC (Mark Felder) >> 4. Re: Help Wanted - Work with MSFT and help finish the port of >> .NET Core to FreeBSD (Mark Felder) >> 5. ?????? - ?? ?? ????????? ? ??????? ? ?? ???????? >> (????????? ??????) >> 6. [Bug 232060] lang/mono: Fix for Mono build on FreeBSD PowerPC >> (bugzilla-noreply@freebsd.org) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Tue, 09 Oct 2018 11:56:24 -0500 >> From: Mark Felder >> To: freebsd-mono@freebsd.org >> Subject: Re: Mono on PowerPC64 >> Message-ID: >> <1539104184.1673855.1536151984.78F7EC7E@webmail.messagingengine.com> >> Content-Type: text/plain; charset="utf-8" >> >> >> >> On Sun, Oct 7, 2018, at 16:51, Curtis Hamilton wrote: >>> I'm working to get the current Mono release to build on PowerPC64 >>> (64-bit). >>> >>> I wanted to check if anyone has experience with building Mono on >>> non-X86 platforms. I'm sure that no one has build Mono on >>> FreeBSD/PowerPC because there is an error in >>> "mono/utils/mono-sigcontext.h" that prevents Mono from building, >>> 32-bit. The code in question is: >> Justin Hibbits did this work in the past, IIRC, but he hasn't worked >> on PPC/PPC64 mono in several years. >> >>