From: Razvan Lixandru <razlix77@gmail.com>
To: 74470@debbugs.gnu.org
Subject: bug#74470: Bug: guile-fibers@1.1.1 arm crosscompile fails due to patch on 1.3.1 version
Date: Fri, 22 Nov 2024 10:46:13 +0200 [thread overview]
Message-ID: <CAEZ231AzCeRQfFc4mC=CyQMwmQB7wFxsxN-7Azjyqg_eHiqP_A@mail.gmail.com> (raw)
Hello,
It looks like this commit:
https://git.savannah.gnu.org/cgit/guix.git/commit/gnu/packages/guile-xyz.scm?id=20c7b8dd04e421a139a02438cf1ddfdfe544a446
causes guile-fiber@1.1.1 which is pulled by shepherd to fail:
phase `unpack' succeeded after 0.0 seconds
starting phase `apply-cross-build-fix-patch'
patching file build-aux/guile.am
Hunk #1 FAILED at 22.
1 out of 1 hunk FAILED -- saving rejects to file build-aux/guile.am.rej
error: in phase 'apply-cross-build-fix-patch': uncaught exception:
%exception #<&invoke-error program: "patch" arguments: ("--force"
"-p1" "-i" "/gnu/store/97r1rrxa9ghrj5qp3din1pg6p2lcpzyv-guile-fibers-cross-build-fix.patch")
exit-status: 1 term-signal: #f stop-signal: #f>
phase `apply-cross-build-fix-patch' failed after 0.0 seconds
command "patch" "--force" "-p1" "-i"
"/gnu/store/97r1rrxa9ghrj5qp3din1pg6p2lcpzyv-guile-fibers-cross-build-fix.patch"
failed with status 1
build process 18 exited with status 256
This happens on both arm-linux-gnueabihf and arm64-linux-gnu.
I think it is happening because the 1.1.1 version inherits 1.3.1.
package and it overrides the source, but the patch is still being
applied.
I guess this brakes all arm* crossbuilds.
Cheers,
Razvan
next reply other threads:[~2024-11-22 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 8:46 Razvan Lixandru [this message]
2024-11-22 12:15 ` bug#74470: Bug: guile-fibers@1.1.1 arm crosscompile fails due to patch on 1.3.1 version janneke
[not found] ` <CAEZ231C7URCzUtsyaYLcDU_1xpNTevhWZcGR=9Jd2qYQZxnRYw@mail.gmail.com>
2024-11-22 21:21 ` janneke
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='CAEZ231AzCeRQfFc4mC=CyQMwmQB7wFxsxN-7Azjyqg_eHiqP_A@mail.gmail.com' \
--to=razlix77@gmail.com \
--cc=74470@debbugs.gnu.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).