For the benefit of future readers: this turned out to be gcc compiler bugs
in the versions we were using.
On nealef-s390x-1 we are using gcc 4.4.7. Neale sent
https://github.com/mono/mono/pull/2488 to workaround this problem which
worked fine there.
However, it broke the build on nealef-s390x-2
Hey,
Are you sure you’re running this on the nealef-s390x-2 machine and not
nealef-s390x-1 ?
This sounds exactly like the problem with the ancient gcc we ran into on the -1
machine, that’s why we’re only using the -2 machine on Jenkins now.
In fact, my IRC log shows we discussed this back in
Re: bugzilla 37781
On the same virtual machine in which the Jenkins bot successfully builds
mono, I am encountering failures of an unusual type. Thinking it might be
a hangover to something in the account’s home directory, I created a
completely new account, cloned from master, configured and
Hi,
If this used to work, you can try git bisect-ing it. Since its an s390x
problem, I'd guess it has to do with endianness.
Zoltan
On Tue, Jan 19, 2016 at 9:13 PM, Neale Ferguson
wrote:
> Re: bugzilla 37781
>
> On the same virtual machine in which the