expect: modify fixline1 script

fixline1 needs to be processed by fixline1, but we
short-circuit that.  Enter the multi-line shebang which
I am a bit queasy about, but expect loves it.

(From OE-Core rev: 0829d4f2947be2b095e7e713b5100f4e41218bec)

Signed-off-by: Joe Slater <joe.slater@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Joe Slater 2022-03-15 15:45:37 -07:00 committed by Richard Purdie
parent 552b8ede77
commit 7f736a56e9
2 changed files with 32 additions and 0 deletions

View File

@ -0,0 +1,31 @@
From eef7c44c10de32ba399ab162cb5799fafdce3fa5 Mon Sep 17 00:00:00 2001
From: Joe Slater <joe.slater@windriver.com>
Date: Tue, 15 Mar 2022 22:00:04 +0000
Subject: [PATCH] fixline1: fix line 1
Ironically, fixline1 needs its first line modified by
fixline1. We do that, manually.
Upstream-Status: Inappropriate [OE specific cross build setup]
Signed-off-by: Joe Slater <joe.slater@windriver.com>
---
fixline1 | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/fixline1 b/fixline1
index 113e9bb..8a38e96 100755
--- a/fixline1
+++ b/fixline1
@@ -1,4 +1,7 @@
-#!expect --
+#!/bin/sh
+# expect won't see the exec \
+exec expect -- "$0" ${1+"$@"}
+
# Synopsis: fixline1 newpath < input > output
# Author: Don Libes
--
2.32.0

View File

@ -25,6 +25,7 @@ SRC_URI = "${SOURCEFORGE_MIRROR}/expect/Expect/${PV}/${BPN}${PV}.tar.gz \
file://0001-Resolve-string-formatting-issues.patch \
file://0001-expect-Fix-segfaults-if-Tcl-is-built-with-stubs-and-.patch \
file://0001-exp_main_sub.c-Use-PATH_MAX-for-path.patch \
file://0001-fixline1-fix-line-1.patch \
"
SRC_URI[md5sum] = "00fce8de158422f5ccd2666512329bd2"
SRC_URI[sha256sum] = "49a7da83b0bdd9f46d04a04deec19c7767bb9a323e40c4781f89caf760b92c34"