On Sat, 13 Jun 2020 15:36:09 + (UTC)
John Klos wrote:
> >>> I'm testing very recent -current on RPi4.
> >>
> >> Threaded programs are broken for aarch64 since ~1 week (most of the
> >> pthread tests fail, programs get stuck in jemalloc cleanup on
> >> thread exit). It is not clear what goes
I'm testing very recent -current on RPi4.
Threaded programs are broken for aarch64 since ~1 week (most of the
pthread tests fail, programs get stuck in jemalloc cleanup on thread
exit). It is not clear what goes wrong exactly (or: why this works on
other architectures)
OK thanks for the info,
On Sat, 13 Jun 2020 07:45:33 +0200
Martin Husemann wrote:
> On Fri, Jun 12, 2020 at 06:21:29PM +0100, Sad Clouds wrote:
> > I'm testing very recent -current on RPi4.
>
> Threaded programs are broken for aarch64 since ~1 week (most of the
> pthread tests fail, programs get stuck in jemalloc
On Fri, Jun 12, 2020 at 06:21:29PM +0100, Sad Clouds wrote:
> I'm testing very recent -current on RPi4.
Threaded programs are broken for aarch64 since ~1 week (most of the
pthread tests fail, programs get stuck in jemalloc cleanup on thread exit).
It is not clear what goes wrong exactly (or: why
I'm testing very recent -current on RPi4. Tried using pkgsrc, but the
following command causes ctfmerge to spin on CPU in what looks like
infinite loop. Not sure if this is specific to ARM port. Any ideas?
# link cwrappers-20180325/imake-wrapper
gcc
