Re: Signal 4 (ILL) caught by ps in mock

2020-02-17 Thread Christoph Junghans
On Mon, Feb 17, 2020 at 3:45 AM Dan Horák wrote: > > On Mon, 17 Feb 2020 11:26:30 +0100 > Petr Pisar wrote: > > > On Fri, Feb 14, 2020 at 02:33:15PM -0700, Christoph Junghans wrote: > > > On Fri, Feb 14, 2020 at 10:37 AM Dan Horák wrote: > > > > > > > > On Fri, 14 Feb 2020 10:28:10 -0700 > > >

Re: Signal 4 (ILL) caught by ps in mock

2020-02-17 Thread Christoph Junghans
On Mon, Feb 17, 2020 at 3:27 AM Petr Pisar wrote: > > On Fri, Feb 14, 2020 at 02:33:15PM -0700, Christoph Junghans wrote: > > On Fri, Feb 14, 2020 at 10:37 AM Dan Horák wrote: > > > > > > On Fri, 14 Feb 2020 10:28:10 -0700 > > > Christoph Junghans wrote: > > > > > > > >> > > > > >> In your case

Re: Signal 4 (ILL) caught by ps in mock

2020-02-17 Thread Dan Horák
On Mon, 17 Feb 2020 11:26:30 +0100 Petr Pisar wrote: > On Fri, Feb 14, 2020 at 02:33:15PM -0700, Christoph Junghans wrote: > > On Fri, Feb 14, 2020 at 10:37 AM Dan Horák wrote: > > > > > > On Fri, 14 Feb 2020 10:28:10 -0700 > > > Christoph Junghans wrote: > > > > > > > >> > > > > >> In your

Re: Signal 4 (ILL) caught by ps in mock

2020-02-17 Thread Petr Pisar
On Fri, Feb 14, 2020 at 02:33:15PM -0700, Christoph Junghans wrote: > On Fri, Feb 14, 2020 at 10:37 AM Dan Horák wrote: > > > > On Fri, 14 Feb 2020 10:28:10 -0700 > > Christoph Junghans wrote: > > > > > >> > > > >> In your case procps-ng package seems to be miscompiled (or run on > > > >> an

Re: Signal 4 (ILL) caught by ps in mock

2020-02-14 Thread Christoph Junghans
On Fri, Feb 14, 2020 at 10:37 AM Dan Horák wrote: > > On Fri, 14 Feb 2020 10:28:10 -0700 > Christoph Junghans wrote: > > > >> > > >> In your case procps-ng package seems to be miscompiled (or run on > > >> an incopatible hardware). I recommend getting a shell in the mock > > >> enviroment (mock

Re: Signal 4 (ILL) caught by ps in mock

2020-02-14 Thread Dan Horák
On Fri, 14 Feb 2020 10:28:10 -0700 Christoph Junghans wrote: > >> > >> In your case procps-ng package seems to be miscompiled (or run on > >> an incopatible hardware). I recommend getting a shell in the mock > >> enviroment (mock --shell) and investigeting whether the ps program > >> works

Re: Signal 4 (ILL) caught by ps in mock

2020-02-14 Thread Christoph Junghans
On Fri, Feb 14, 2020 at 6:38 AM Christoph Junghans wrote: > > > > On Fri, Feb 14, 2020, 00:16 Petr Pisar wrote: >> >> On Thu, Feb 13, 2020 at 07:48:22PM -0700, Christoph Junghans wrote: >> > when running "mock -r fedora-rawhide-ppc64le --no-clean >> > gromacs-2019.5-2.fc32.1.src.rpm" >> > I am

Re: Signal 4 (ILL) caught by ps in mock

2020-02-14 Thread Christoph Junghans
On Fri, Feb 14, 2020, 00:16 Petr Pisar wrote: > On Thu, Feb 13, 2020 at 07:48:22PM -0700, Christoph Junghans wrote: > > when running "mock -r fedora-rawhide-ppc64le --no-clean > > gromacs-2019.5-2.fc32.1.src.rpm" > > I am getting the following error: > > Signal 4 (ILL) caught by ps (3.3.15). > >

Re: Signal 4 (ILL) caught by ps in mock

2020-02-13 Thread Petr Pisar
On Thu, Feb 13, 2020 at 07:48:22PM -0700, Christoph Junghans wrote: > when running "mock -r fedora-rawhide-ppc64le --no-clean > gromacs-2019.5-2.fc32.1.src.rpm" > I am getting the following error: > Signal 4 (ILL) caught by ps (3.3.15). > /usr/bin/ps:ps/display.c:66: please report this bug > > I