From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] make.sh: Fixes for rust (1.65)
Date: Thu, 01 Dec 2022 16:01:40 +0100 [thread overview]
Message-ID: <20221201150140.2932973-1-matthias.fischer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
During updating rust to 1.65 I found that 'lfsmake2 rust' appeared
twice and removed the second - obsolete - call.
'rust-cipher' now requires 'rust-crypto-common', but was called later
in the build sequence.
=> Moved 'rust-crypto-common' just before 'rust-cipher'. [Thanks Adolf! ;-)]
Signed-off-by: Matthias Fischer <matthias.fischer(a)ipfire.org>
---
make.sh | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/make.sh b/make.sh
index 413d04491..e256e2755 100755
--- a/make.sh
+++ b/make.sh
@@ -1203,7 +1203,6 @@ buildipfire() {
lfsmake2 sqlite
lfsmake2 libffi
lfsmake2 python3
- lfsmake2 rust
lfsmake2 rust-dissimilar
lfsmake2 rust-cfg-if
lfsmake2 rust-libc
@@ -1211,6 +1210,7 @@ buildipfire() {
lfsmake2 rust-typenum
lfsmake2 rust-version-check
lfsmake2 rust-generic-array
+ lfsmake2 rust-crypto-common
lfsmake2 rust-cipher
lfsmake2 rust-hex
lfsmake2 rust-unicode-xid
@@ -1237,7 +1237,6 @@ buildipfire() {
lfsmake2 rust-serde_json
lfsmake2 rust-synstructure
lfsmake2 rust-block-buffer
- lfsmake2 rust-crypto-common
lfsmake2 rust-digest
lfsmake2 rust-ppv-lite86
lfsmake2 rust-rand_core
--
2.34.1
reply other threads:[~2022-12-01 15:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221201150140.2932973-1-matthias.fischer@ipfire.org \
--to=matthias.fischer@ipfire.org \
--cc=development@lists.ipfire.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox