Re: Bug#819711: Fails to build mono when PPC_64K_PAGES is set

2016-10-01 Thread Jo Shields
On 01/10/16 13:50, Mathieu Malaterre wrote: > I am building also on PowerMac G4 ATM to > double check any possible regression. Let me know. I intend to upload 4.6 next week, which already includes your changes. You might want to try throwing http://download.mono-project.com/repo/debian/pool/main

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2016-03-31 Thread Jo Shields
On 31/03/16 11:49, Mathieu Malaterre wrote: > While at it, I was wondering why a portion of the patch did not make > it into Debian: > > https://bugzilla.xamarin.com/show_bug.cgi?id=28679#c9 > > + /* It is expected to be a function descriptor on power pre-v2 ABI */ > + buf = mono_create_ftnptr

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-09 Thread Jo Shields
On 09/09/15 15:08, Lennart Sorensen wrote: > On Wed, Sep 09, 2015 at 08:27:44AM +0100, Jo Shields wrote: >> It's not the silicon - it failed on a G5 XServe as well >> >> It's not gcc - I did a successful build on gcc5. >> >> It's not the kernel ver

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-09 Thread Jo Shields
On 08/09/15 16:40, Lennart Sorensen wrote: > On Tue, Sep 08, 2015 at 04:24:10PM +0100, Jo Shields wrote: >> 3.16.0-4-powerpc64 >> >> partch.debian.org, the porterbox where it fails: >> cpu: POWER7 (architected), altivec supported >> model: IBM,823

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-08 Thread Jo Shields
On 08/09/15 16:08, Lennart Sorensen wrote: > On Mon, Sep 07, 2015 at 03:42:03PM +0100, Jo Shields wrote: >> I can get things in under a "trivial" exception. One patch is in, the >> other is stuck in "please rewrite this" hell @ >> https://github.com/mono/

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-07 Thread Jo Shields
On 07/09/15 15:42, Jo Shields wrote: > Any bright ideas from anyone else in the peanut gallery? It seems dumb > as hell to be to need to pull the package when it *does* work - just not > on the right computer for it to be considered "fine". > This is where we are, havin

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-07 Thread Jo Shields
On 01/09/15 16:42, Lennart Sorensen wrote: > On Tue, Sep 01, 2015 at 09:48:54AM +0100, Jo Shields wrote: >> If you can sign the CLA at https://cla.xamarin.com/ I can take care of >> the patch process > Well I looked at it and it would seem I can not. > > I am employed b

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-09-01 Thread Jo Shields
On 28/08/15 18:58, Lennart Sorensen wrote: > Assuming GH means github, then I have no idea how one would do that. > I only ever just pull things from github. If you can sign the CLA at https://cla.xamarin.com/ I can take care of the patch process > Certainly getting the fixes in would be great,

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-28 Thread Jo Shields
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 26/08/15 22:14, Lennart Sorensen wrote: > Patch I did, which worked this well on the first try, but I won't > say it is perfect for sure (and I suspect if it makes sense, then > ppc64 could add the instructions to their .md file too). > > diff

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-26 Thread Jo Shields
On 26/08/15 22:44, Lennart Sorensen wrote: I managed to get failure 1 and 2 above to go away by changing the test slightly: diff --git a/mcs/class/corlib/Test/System/DateTimeTest.cs b/mcs/class/corlib/Test/System/DateTimeTest.cs index 0e3076b..2db099c 100644 --- a/mcs/class/corlib/Test/Syste

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-26 Thread Jo Shields
On 26/08/15 20:12, Lennart Sorensen wrote: On Wed, Aug 26, 2015 at 07:01:31PM +0100, Jo Shields wrote: On 26/08/15 18:47, Lennart Sorensen wrote: Opcode 'move_f_to_i4' missing from machine description file. I agree with its assessment, there's no OP_MOVE_F_TO_I4 in mono/

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-26 Thread Jo Shields
On 26/08/15 18:47, Lennart Sorensen wrote: Opcode 'move_f_to_i4' missing from machine description file. I agree with its assessment, there's no OP_MOVE_F_TO_I4 in mono/mini/mini-ppc.c and no move_f_to_i4 in mono/mini/cpu-ppc.md (maybe there should be? other arches have it)

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-26 Thread Jo Shields
On 26/08/15 17:26, Lennart Sorensen wrote: > > And running the test suite as NOT root solved that. So now the only > problem I see left in 'make mcs-do-tests' is getting stuck forever in > one test: > > make[9]: Entering directory '/tmp/mono-new/mono-1/mcs/class/corlib' > ok=:; \ > PATH="/tmp/mo

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-26 Thread Jo Shields
On 26/08/15 17:16, Lennart Sorensen wrote: > > And a patch that fixes that (since the double's stored in the table are > little endian, they have to be endian swapped before being returned as > a double). > > diff --git a/mscorlib/system/globalization/charunicodeinfo.cs > b/mscorlib/system/globa

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-25 Thread Jo Shields
On 25/08/15 22:29, Lennart Sorensen wrote: > I had thought that could be it too. I certainly haven't seen that > particular problem so far. Are you simply running make or are you > passing any arguments to configure or anything? I tried using a copy > of the debian dir from the mono package in ex

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-25 Thread Jo Shields
On 25/08/15 22:01, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 09:28:50PM +0100, Jo Shields wrote: >> Okay, now I'm confused? The point of that branch was it was the >> almost-working state, the compiler was one of the things not working >> properly! Let me tr

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-25 Thread Jo Shields
On 25/08/15 19:33, Lennart Sorensen wrote: > I am currently running make compiler-tests, which is currently "stuck" > after doing something and seems to be using no cpu but waiting 2 > seconds again and again for soem futex. Okay, now I'm confused? The point of that branch was it was the almost-

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-25 Thread Jo Shields
On 25/08/15 16:34, Lennart Sorensen wrote: > On Tue, Aug 25, 2015 at 10:53:31AM -0400, Lennart Sorensen wrote: >> On Tue, Aug 25, 2015 at 10:09:58AM -0400, Lennart Sorensen wrote: >>> OK, I was just trying what README.md said to do when using the get >>> monolite option. >>> >>> I also just notic

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-25 Thread Jo Shields
On 25/08/15 14:44, Lennart Sorensen wrote: > > I did that, and got a ton of other errors. > > The readme file said to use: > > make get-monolite-latest > make EXTERNAL_MCS=${PWD}/mcs/class/lib/monolite/basic.exe Don't touch EXTERNAL_MCS - if set, it needs to be the path to an executable compiler

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-24 Thread Jo Shields
On 24/08/15 22:49, Lennart Sorensen wrote: On Sun, Aug 16, 2015 at 08:59:19AM +0100, Jo Shields wrote: Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I don't want to delay it. It doesn'

Re: Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-16 Thread Jo Shields
On 16/08/15 11:00, Mathieu Malaterre wrote: On Sun, Aug 16, 2015 at 9:59 AM, Jo Shields <mailto:direct...@apebox.org>> wrote: Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I d

Potential Mono removal from 32-bit big endian PowerPC in next upload

2015-08-16 Thread Jo Shields
Dear PPC porter people, The major Mono version pending in experimental fixes GCC5 and fixes reproducible builds and a dozen other bugs, so I don't want to delay it. It doesn't build on PowerPC any more, and nobody upstream is working on it. We recently introduced ppc64el, which is working, bu