From: Maxime Devos <maximedevos@telenet.be>
To: 路辉 <luhux76@gmail.com>, 57857@debbugs.gnu.org
Subject: [bug#57857] [PATCH] gnu: busybox: fix the cross build.
Date: Fri, 16 Sep 2022 17:08:33 +0200 [thread overview]
Message-ID: <3044d0d3-8a3b-baf7-b86b-55960e77eec1@telenet.be> (raw)
In-Reply-To: <CAGNyvegvZJ2sWuUrzqDwAPKUfc7K0Fcs5L4h5FQMkG=CCfvBEg@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1225 bytes --]
On 16-09-2022 14:35, 路辉 wrote:
>
+ (if tests?
+ (apply invoke "make"
+ ;; "V=1"
+ "SKIP_KNOWN_BUGS=1"
+ "SKIP_INTERNET_TESTS=1"
+ "check" make-flags)
+ #t)))
Can be simplified to
(when tests?
(apply invoke "make"
;; "V=1"
"SKIP_KNOWN_BUGS=1"
"SKIP_INTERNET_TESTS=1"
"check" make-flags))
+ `(#:tests? (if ,(%current-target-system) #f #t)
That's the default, no need to mention it again here.
+ #:make-flags
+ (let ((target ,(%current-target-system)))
+ (if target
+ (list (string-append "CROSS_COMPILE=" target "-"))
+ (list)))
Can be simplified:
#:make-flags
,(let ((target ,(%current-target-system)))
(if target
#~(list (string-append "CROSS_COMPILE=" ,target))
#~'()))
(the #~ makes the phasing more explicit, if you go for that, I recommend
turning the arguments into (arguments (list #:phases #~(modify-phases
...) #:make-flags ...)), instead of using ` / , , to remain consistent.)
Greetings,
Maxime
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2022-09-16 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 12:35 [bug#57857] [PATCH] gnu: busybox: fix the cross build 路辉
2022-09-16 15:08 ` Maxime Devos [this message]
2022-09-16 15:53 ` 路辉
2022-09-25 17:55 ` Maxime Devos
2022-09-26 21:27 ` bug#57857: " Ludovic Courtès
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=3044d0d3-8a3b-baf7-b86b-55960e77eec1@telenet.be \
--to=maximedevos@telenet.be \
--cc=57857@debbugs.gnu.org \
--cc=luhux76@gmail.com \
/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).