From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@reproducible-builds.org>
Cc: 44827@debbugs.gnu.org
Subject: bug#44827: tests/channels.scm: Test failures building on Debian i386 or armhf with libgit2-dev 1.0.1
Date: Thu, 26 Nov 2020 22:45:32 +0100 [thread overview]
Message-ID: <877dq723nn.fsf@gnu.org> (raw)
In-Reply-To: <87wnybhmpq.fsf@yucca> (Vagrant Cascadian's message of "Mon, 23 Nov 2020 11:55:45 -0800")
Hi,
Vagrant Cascadian <vagrant@reproducible-builds.org> skribis:
> Updating the build dependency to libgit2-dev >= 1.0.1 (which pulls in a
> similar version to what guix is using) fixes test suite failures ... but
> only on the amd64 architecture. The same tests pass Using an older
> version of libgit2-dev (0.28). FWIW, this is building with guile-3.0.
[...]
> actual-error:
> + (git-error
> + #<<git-error> code: -1 message: "invalid version 0 on git_proxy_options" class: 3>)
This error is the sign of an ABI mismatch issue between Guile-Git and
libgit2 (like Guile-Git assuming a wrong layout for one of the C structs
exposed by libgit2).
Which version of Guile-Git are you using? Do its tests pass?
In particular, Guile-Git 0.4.0 has this thing compile-time check to make
sure it matches the ABI of the underlying libgit2 version (0.28 or 1.0):
https://gitlab.com/guile-git/guile-git/-/commit/2b4d077c6f55648f42af31ae783ca4d8c1c5f1de
So if you change libgit2 versions, you need to rebuild Guile-Git.
HTH,
Ludo’.
next prev parent reply other threads:[~2020-11-26 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 19:55 bug#44827: tests/channels.scm: Test failures building on Debian i386 or armhf with libgit2-dev 1.0.1 Vagrant Cascadian
2020-11-26 21:45 ` Ludovic Courtès [this message]
2020-11-27 7:22 ` Vagrant Cascadian
2020-11-27 10:02 ` Ludovic Courtès
2020-11-27 22:20 ` Vagrant Cascadian
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877dq723nn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44827@debbugs.gnu.org \
--cc=vagrant@reproducible-builds.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.