unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Guillaume Le Vaillant <glv@posteo.net>
To: guix-devel <guix-devel@gnu.org>
Cc: Vagrant Cascadian <vagrant@debian.org>
Subject: Re: Some packages failing to build
Date: Fri, 15 May 2020 17:40:21 +0200	[thread overview]
Message-ID: <87y2pt5hqy.fsf@yamatai> (raw)
In-Reply-To: <87r1vmh6uc.fsf@yamatai>

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


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

> 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.

Update: bitcoin-abc and bitcoin-unlimited updated/fixed.

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

      reply	other threads:[~2020-05-15 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-09 14:27 Some packages failing to build Guillaume Le Vaillant
2020-05-10  8:36 ` Guillaume Le Vaillant
2020-05-10 20:30   ` Marius Bakke
2020-05-10 21:45     ` Vagrant Cascadian
2020-05-11  9:38       ` Guillaume Le Vaillant
2020-05-14 15:30         ` Guillaume Le Vaillant
2020-05-15 15:40           ` Guillaume Le Vaillant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y2pt5hqy.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).