2011/10/3 solarflow99 <solarflow99@gmail.com>:

> I have a strange problem here, my package will build fine, but if anyone
> tries to run it, the dam thing just hangs.
> I can build in mock on my own system and it runs just fine. Others are
> starting to report this bug against the package so know its not just me.
>
> https://bugzilla.rpmfusion.org/show_bug.cgi?id=1959
>
>
> I can compare the binary is different from rpmfusion and my own build:
>
> 1828572 Oct 3 02:39 /usr/bin/dosemu.bin
> 1834428 Sep 9 01:07 /usr/bin/dosemu.bin - The bad one from rpmfusion
> build
>
> The build logs seem almost identical. Does anyone know why there might be
> something different? Are all updates applied on the builder? I see some
> minor version differences, however the bad binary was compiled almost a
> month ago.
>
> Any suggestions at all?

Does this appear on all target or only for F-16 ?
Can you resubmit a job?
build.log can be the same but root.log are probably not. That's a more
probable path before to consider a problem on the builder.

Right now we have the updates-testing repository enabled. This
probably shouldn't be kept.
This has helped a lot when building kernel modules and others packages
that would have needed an override, but has leaded to issues with
packages hardcode a matching version (perl qt mostly).

Hi, thanks for your suggestions, it looks like it was rpmfusion just happened to have a difference in CFLAGS used, which happened to trigger a bug in this package. Dosemu uses some attribute((constructor)) functions that get called before main. The order isn't known (for newer GCCs you can set priorities but they are not used). Somehow the RPMFusion build ended up with an order that triggered the hang (that has, in principle been present in dosemu for many years), a linked-list where an element referenced itself.

Is there any way to see what URL's are being used by mock for the builder? I want to build in mock with exactly the same repos as rpmfusion is using.