From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Cc: Adolf Belka <adolf.belka@ipfire.org>
Subject: [PATCH 2/4] make.sh: Add expect into the lfsmake2 list
Date: Thu, 30 Oct 2025 11:18:28 +0100 [thread overview]
Message-ID: <20251030101830.30837-2-adolf.belka@ipfire.org> (raw)
In-Reply-To: <20251030101830.30837-1-adolf.belka@ipfire.org>
- With expect available in the main build section the hack of having --enable-toolchain
used for it is no longer needed.
Signed-off-by: Adolf Belka <adolf.belka@ipfire.org>
---
make.sh | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/make.sh b/make.sh
index 5bdc7690c..3f642ae2a 100755
--- a/make.sh
+++ b/make.sh
@@ -2067,7 +2067,8 @@ build_system() {
lfsmake2 mcelog
lfsmake2 socat
lfsmake2 libtpms
- lfsmake2 --enable-toolchain swtpm # requires expect from the toolchain
+ lfsmake2 expect
+ lfsmake2 swtpm
lfsmake2 libpciaccess
lfsmake2 ovmf
lfsmake2 libvirt
--
2.51.1
next prev parent reply other threads:[~2025-10-30 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 10:18 [PATCH 1/4] expect: Allow build of expect for swtpm Adolf Belka
2025-10-30 10:18 ` Adolf Belka [this message]
2025-10-30 10:18 ` [PATCH 3/4] tcl: install private headers for expect to use in build Adolf Belka
2025-10-30 10:18 ` [PATCH 4/4] core199: Ship expect and tcl Adolf Belka
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=20251030101830.30837-2-adolf.belka@ipfire.org \
--to=adolf.belka@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