DevHeads.net

Debugging ppc64le

Hi,

While packaging up votca-csg-1.5, I ran into some tests failing:
<a href="https://github.com/votca/csg/issues/326" title="https://github.com/votca/csg/issues/326">https://github.com/votca/csg/issues/326</a>
but this only happens on ppc64le under epel7. (So I expect boost-1.53
being the culprit!)

Is there a good way (qemu or something) to debug this interactively?

Cheers,

Christoph

Comments

Re: Debugging ppc64le

By =?ISO-8859-2?Q?... at 02/06/2019 - 08:10

Dne 06. 02. 19 v 1:47 Christoph Junghans napsal(a):
<a href="https://github.com/rpm-software-management/mock/wiki/Feature-forcearch" title="https://github.com/rpm-software-management/mock/wiki/Feature-forcearch">https://github.com/rpm-software-management/mock/wiki/Feature-forcearch</a>

Miroslav

Re: Debugging ppc64le

By Christoph Junghans at 02/06/2019 - 12:43

On Wed, Feb 6, 2019 at 5:11 AM Miroslav Suchý < ... at redhat dot com> wrote:
Christoph

Re: Debugging ppc64le

By Tom Hughes at 02/05/2019 - 20:51

You can use one of the test machines:

<a href="https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers" title="https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers">https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Mainta...</a>

The ppc64le one is F28 but if you can't reproduce it there then
you can use mock to get an EPEL7 environment.

Tom

Re: Debugging ppc64le

By Serge Guelton at 02/06/2019 - 03:21

On Wed, Feb 06, 2019 at 12:51:54AM +0000, Tom Hughes wrote:
I've been in the same situation to debug <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1672630" title="https://bugzilla.redhat.com/show_bug.cgi?id=1672630">https://bugzilla.redhat.com/show_bug.cgi?id=1672630</a>
And I ended up asking for an account on <a href="https://cfarm.tetaneutral.net/" title="https://cfarm.tetaneutral.net/">https://cfarm.tetaneutral.net/</a>, they do have a few ppc
machine available.

Hop it helps