On Tue, 15 Mar 2016 23:37:26 +0100
=?UTF-8?B?TMOhc3psw7MgQsO2c3rDtnJtw6lueWkgKEdDUyk=?= <g...@debian.org> wrote:
On Tue, Mar 15, 2016 at 11:24 PM, Julian Taylor
<jtaylor.deb...@googlemail.com> wrote:
> On 15.03.2016 22:48, László Böszörményi (GCS) wrote:
>> This is known to pyzmq upstream[1] for about three years. It happens
>> on Ubuntu, Red Hat, CentOS and with ZeroMQ 4.0.x as well. While
>> timer_create() [4] is in librt, the standard GNU C library, it seems
>> pyzmq miss to link with it on the failing architectures.
[...]
> Are you saying linking against -lrt will fix the tests deadlocking?
>
> I don't quite see the relation between the hanging tests and the linked
> issues.
> The implicit declaration errors have always been there I think but only
> in a configure check so harmless (until now?).
While I was checking the failing build logs, I see:
build/temp.linux-armv7l-2.7/scratch/tmp/timer_createOfMQXG.o: In
function `main':
timer_createOfMQXG.c:(.text+0x14): undefined reference to `timer_create'
collect2: error: ld returned 1 exit status
It's not just the implicit declaration, but a linker error later. I
can be wrong, but it seems it _may_ cause the test hang as there's no
timer to look for / to wait its expiration. Sorry if it happens in
normal logs as well; will check it tomorrow morning as it's almost
midnight here. :(
Got a chance to look at this?
Emilio
