[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FAIL: test-rwlock1 on 32-bit ARM
|
From: |
Bruno Haible |
|
Subject: |
Re: FAIL: test-rwlock1 on 32-bit ARM |
|
Date: |
Tue, 06 Feb 2018 18:11:35 +0100 |
|
User-agent: |
KMail/5.1.3 (Linux/4.4.0-104-generic; KDE/5.18.0; x86_64; ; ) |
Hi,
Jeffrey Walton wrote:
> > FAIL: test-rwlock1
> > ==================
> >
> > Unexpected outcome 3
> > FAIL test-rwlock1 (exit status: 134)
> >
> > Any ideas what I might be doing wrong?
"Unexpected outcome 3" means that the test program could not create a second
thread (other than the main thread). You haven't showed the configure options
and GCC options that you passed; I would guess that they contain an option
that is incompatible to multithreading. Maybe "-static" or something like that?
If so, consider it a normal, expected failure.
Bruno