Guillaume Le Vaillant <glv@posteo.net> skribis:

> Vagrant Cascadian <vagrant@debian.org> skribis:
>
>> On 2020-05-10, Marius Bakke wrote:
>>> Guillaume Le Vaillant <glv@posteo.net> writes:
>>>
>>>> Guillaume Le Vaillant <glv@posteo.net> skribis:
>>>>
>>>>> Hi,
>>>>>
>>>>> After pulling guix with the merged core updates (guix at commit
>>>>> 95ffdfe86cb1b8a8e4fff1386a147718400b76e0), I found a few packages
>>>>> failing to build:
>>>>>
>>>>>  - fbreader
>>>>>  - gnubg
>>>>>  - gnubik
>>>>>  - postgis
>>>>>  - python-cheetah
>>>>>  - python-trezor
>>>>>
>>>>> I have not yet had the time to try and fix them, so I just list them
>>>>> here in case someone wants to take a look at them.
>>>>
>>>> Update: postgis and python-cheetah fixed.
>>>
>>> fbreader, gnubg and gnubik fixed.
>>
>> Updating python-trezor to 0.12.0 fixed it; pushed to master.
>
> Hi, thanks for the fixes.
>
> I found a few other build failures:
>
>  - bitcoin-abc
>  - bitcoin-core
>  - bitcoin-unlimited
>
>
> There is also the wsjtx package that builds fine but starting the
> program fails with:
>
> --8<---------------cut here---------------start------------->8---
> /home/guillaume/.guix-profile/bin/wsjtx: symbol lookup error:
> /home/guillaume/.guix-profile/bin/wsjtx: undefined symbol: fmodf,
> version GLIBCXX_3.4.3
> --8<---------------cut here---------------end--------------->8---
>
> However, doing a "ldd $(guix build wsjtx)/bin/.wsjtx-real" shows that
> the libm.so.6 library that contains the fmodf function is in the
> dependencies. Do you have an idea what could cause the symbol lookup to
> fail?

I pushed a workaround for wsjtx as
b79794a7630a04668d2769aee50ebc25e0d7c3d2. I'm not fully satisfied by
it as I don't yet know why the libraries would get in the wrong order
when linking the program. But well, at least it starts now.