On Wed, Feb 6, 2019 at 5:11 AM Miroslav Suchý wrote:
>
> Dne 06. 02. 19 v 1:47 Christoph Junghans napsal(a):
> > Is there a good way (qemu or something) to debug this interactively?
>
> https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
Thanks, "mock -r epel-7-ppc64le --forcear
Dne 06. 02. 19 v 1:47 Christoph Junghans napsal(a):
> Is there a good way (qemu or something) to debug this interactively?
https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
Miroslav
___
devel mailing list -- devel@lists.fedoraprojec
On Wed, Feb 06, 2019 at 12:51:54AM +, Tom Hughes wrote:
> On 06/02/2019 00:47, Christoph Junghans wrote:
>
> >While packaging up votca-csg-1.5, I ran into some tests failing:
> >https://github.com/votca/csg/issues/326
> >but this only happens on ppc64le under epel7. (So I expect boost-1.53
> >
On 06/02/2019 00:47, Christoph Junghans wrote:
While packaging up votca-csg-1.5, I ran into some tests failing:
https://github.com/votca/csg/issues/326
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
Hi,
While packaging up votca-csg-1.5, I ran into some tests failing:
https://github.com/votca/csg/issues/326
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
--
Chri