[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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



On Wed, Sep 09, 2015 at 03:13:56PM +0100, Jo Shields wrote:
> porpora has the same ppc64 kernel as partch, libc 2.19-19
> 
> That's an interesting idea. Try building from
> http://http.debian.net/debian/pool/main/m/mono/mono_4.0.4.1+dfsg-1.dsc
> which bundles a matched monolite generated from its own sources
> (get-monolite-latest downloads the most recent available monolite with a
> compatible ABI)
> 
> It *could* be related to endian issues in the class library of monolite
> itself

Annoyingly, that builds for me too.  dpkg-buildpackage on the files you
listed work and produce debs.

CPU   |kernel|flavour|libc    |monolite version|status|name
------+------+-------+--------+----------------+------+-------
power8|3.16  |ppc64  |2.19-19 |4.0.4.0         |failed|powerpc-unicamp-01
power7|3.2   |ppc64  |2.19-19 |4.1.0.0         |works |rceng03
power7|3.2   |ppc64  |2.19-19 |4.0.4.0         |works |rceng03
power7|3.16  |ppc64  |?       |4.0.4.0         |failed|partch
mac G5|3.16  |ppc64  |2.19-19 |4.0.4.0         |failed|porpora
mini  |3.16  |ppc    |?       |?               |works |

I have no idea if it matters, but we are running the power7 machine in
unmanaged mode, with no LPAR setup, so just debian on bare metal setup.
I don't know if there is any way that matters, but I would sure hope not.
Code should not segfault on the same type of hardware just because of
how it is being run.

-- 
Len Sorensen


Reply to: