From: "Ludovic Courtès" <ludo@gnu.org>
To: Zheng Junjie <zhengjunjie@iscas.ac.cn>
Cc: 74669@debbugs.gnu.org
Subject: [bug#74669] [PATCH v2] gnu: elfutils: Fix cross-compilation.
Date: Thu, 12 Dec 2024 23:03:13 +0100 [thread overview]
Message-ID: <87ikro5zku.fsf@gnu.org> (raw)
In-Reply-To: <ef0a9f493079ba65abb46295c3101091910f1094.1733331861.git.zhengjunjie@iscas.ac.cn> (Zheng Junjie's message of "Thu, 5 Dec 2024 01:04:21 +0800")
Hi,
Zheng Junjie <zhengjunjie@iscas.ac.cn> skribis:
> * gnu/packages/elf.scm (elfutils): Fix cross-compilation
> [arguments]: When cross-compilation, apply patch.
> [native-inputs]: When cross-compilation, add patch.
> * gnu/packages/patches/elfutils-libdwfl-Rewrite-reading-of-ar_size-in-elf_begin_rand.patch:
> New file.
> * gnu/local.mk (dist_patch_DATA): Register it.
>
> Change-Id: Ia1ab9c09124a140608bda34bf62f0ae80eb44f9b
[...]
> + %D%/packages/patches/elfutils-libdwfl-Rewrite-reading-of-ar_size-in-elf_begin_rand.patch \
Please pick a shorter file name, as noted by ‘guix lint’.
(Like ‘elfutils-libdwfl-string-overflow.patch’.)
> + '((add-after 'unpack 'patch
> + (lambda* (#:key native-inputs #:allow-other-keys)
> + (invoke "patch" "-Np1" "-i"
> + (assoc-ref native-inputs
> + "elfutils-libdwfl-Rewrite-reading-of-ar\
> +_size-in-elf_begin_rand.patch")))))
Could you use a gexp instead? And ‘--force’ is better suited than ‘-N’
I think.
#~(add-after …
…
(invoke "patch" "-p1" "--force" "-i" #$(local-file (search-patch …))))
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-12-12 22:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-03 12:18 [bug#74669] [PATCH] gnu: elfutils: Fix cross-compilation Zheng Junjie
2024-12-04 17:04 ` [bug#74669] [PATCH v2] " Zheng Junjie
2024-12-12 22:03 ` Ludovic Courtès [this message]
2024-12-13 13:05 ` [bug#74669] [PATCH v3] " Zheng Junjie
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=87ikro5zku.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=74669@debbugs.gnu.org \
--cc=zhengjunjie@iscas.ac.cn \
/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).