Re: Some packages failing to build

[Guillaume Le Vaillant <glv@posteo.net>]

[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]


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?

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]