From: "宋文武 via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: Christopher Howard <christopher@librehacker.com>
Cc: 64340-done@debbugs.gnu.org
Subject: bug#64340: libsigrokdecode: check phase fails
Date: Sun, 27 Aug 2023 10:23:32 +0800 [thread overview]
Message-ID: <87v8d1w7dn.fsf@envs.net> (raw)
In-Reply-To: <ZJytXLfT8mBjFwAg@theoden> (Christopher Howard's message of "Wed, 28 Jun 2023 13:59:56 -0800")
Christopher Howard <christopher@librehacker.com> writes:
> I am trying to install pulseview, but libsigrokdecode fails to build,
> dying at the check phase. It appears to be a dependency-related issue
> - test programs cannot build do to undefined functions.
>
> ```
> ld: ./.libs/libsigrokdecode.so: undefined reference to `PyList_Insert'
> ld: ./.libs/libsigrokdecode.so: undefined reference to `PyModule_AddObject'
> ld: ./.libs/libsigrokdecode.so: undefined reference to `PySys_GetObject'
> <<<snip>>>
> ld: ./.libs/libsigrokdecode.so: undefined reference to `PyUnicode_AsUTF8String'
> ld: ./.libs/libsigrokdecode.so: undefined reference to `Py_IsInitialized'
> ld: ./.libs/libsigrokdecode.so: undefined reference to `PyDict_New'
> collect2: error: ld returned 1 exit status
> make[1]: *** [Makefile:751: tests/main] Error 1
> make: *** [Makefile:1353: check-am] Error 2
>
> Test suite failed, dumping logs.
> error: in phase 'check': uncaught exception:
> %exception #<&invoke-error program: "make" arguments: ("check" "-j"
> "4") exit-status: 2 term-signal: #f stop-signal: #f>
> phase `check' failed after 0.5 seconds
> command "make" "check" "-j" "4" failed with status 2
> ```
>
> Full build log is attached.
>
> I see an open bug at <https://issues.guix.gnu.org/63971>, but I'm not sure if this is the same issue or not.
>
Thanks for the report, and I had fixed it by apply update for
libsigrokdecode from 63971.
Closing!
prev parent reply other threads:[~2023-08-27 2:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 21:59 bug#64340: libsigrokdecode: check phase fails Christopher Howard
2023-08-27 2:23 ` 宋文武 via Bug reports for GNU Guix [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=87v8d1w7dn.fsf@envs.net \
--to=bug-guix@gnu.org \
--cc=64340-done@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=iyzsong@envs.net \
/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).