From: Efraim Flashner <efraim@flashner.co.il>
To: 宋文武 <iyzsong@envs.net>
Cc: 62432-done@debbugs.gnu.org, Z572 <873216071@qq.com>
Subject: bug#62432: [PATCH] gnu: libicns: fix riscv64 cross-build.
Date: Sun, 4 Jun 2023 15:29:45 +0300 [thread overview]
Message-ID: <ZHyDucbVTMBcJVyc@3900XT> (raw)
In-Reply-To: <878rf9b51p.fsf@envs.net>
[-- Attachment #1: Type: text/plain, Size: 2390 bytes --]
On Mon, Apr 03, 2023 at 07:04:18PM +0800, 宋文武 via Guix-patches via wrote:
> Z572 <873216071@qq.com> writes:
>
> > * gnu/packages/image.scm (libicns): fix riscv64 cross-build.
>
> Hello, this message is already in the commit message title, So I think
> there is no need to repeat it here. Also look in the guix commit log,
> I think it should be 'gnu: libicns: Fix cross-compilation for riscv64'.
>
>
> > + (arguments (if (target-riscv64?)
> > + (list #:phases
> > + #~(modify-phases %standard-phases
> > + (add-after 'unpack 'update-config-scripts
> > + (lambda* (#:key native-inputs inputs #:allow-other-keys)
> > + (for-each (lambda (file)
> > + (install-file
> > + (search-input-file
> > + (or native-inputs inputs)
> > + (string-append "/bin/" file)) "."))
> > + '("config.guess" "config.sub"))))) )
> > + '()))
> > + (native-inputs
> > + (if (target-riscv64?)
> > + (list config)
> > + '()))
>
> This updates 'config.guess' and 'config.sub' in a package to fix
> cross-compilation for riscv64 seems like a common practice (eg: also in
> your patches #62433, #62544). How about make a procedure for it to
> save some typing? It could be:
>
> ```
> (define (autotools-config-updated-package p)
> "Return package P with @command{config.guess} and
> @command{config.sub} updated by the @code{config} package"
> (package (inherit p)
> ...))
> ```
>
> Which could go into (guix transformations).
I would certainly like something like this. I suppose it could be made
more general by using find-file to find all occurrences of config.guess
and config.sub and replacing those.
In the meantime I've pushed this patch after replacing (target-riscv64?)
with (and (target-riscv64?) (%current-target-system)).
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-06-04 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 4:50 [bug#62432] [PATCH] gnu: libicns: fix riscv64 cross-build Z572 via Guix-patches via
2023-04-03 11:04 ` 宋文武 via Guix-patches via
2023-06-04 12:29 ` Efraim Flashner [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=ZHyDucbVTMBcJVyc@3900XT \
--to=efraim@flashner.co.il \
--cc=62432-done@debbugs.gnu.org \
--cc=873216071@qq.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).