无法安装Expect时，如何源码构建并与Shell脚本同目录部署以使用Expect？

Absolutely! This is totally feasible—you can build a statically compiled version of Expect (along with its Tcl dependency) from source, then bundle the standalone binary with your script. This way, your target systems won't need any pre-installed libraries or packages. Here's a detailed step-by-step guide:

1. Grab the source code for Tcl and Expect #

Expect relies on Tcl, so you'll need both:

• Download stable versions (e.g., Tcl 8.6.x and Expect 5.45.x—these have great compatibility) from their official source repositories.
• Extract both archives into a single build directory, like ~/expect-build/.

2. Compile a static Tcl library first #

Since Expect links against Tcl, we need a static Tcl library to ensure no dynamic dependencies:

cd ~/expect-build/tcl8.6.13/unix
./configure --prefix=/tmp/expect-static --enable-static --disable-shared
make
make install

• --prefix sets a temporary install directory for the static build.
• --enable-static forces the build to create static libraries, while --disable-shared turns off dynamic library generation.

3. Compile statically linked Expect #

Next, build Expect and link it against the static Tcl library we just created:

cd ~/expect-build/expect5.45.4
./configure --prefix=/tmp/expect-static \
  --with-tcl=/tmp/expect-static/lib \
  --with-tclinclude=~/expect-build/tcl8.6.13/generic \
  --enable-static --disable-shared
make
make install

• --with-tcl points to the static Tcl library directory.
• --with-tclinclude specifies the path to Tcl's header files.
• The static/disable-shared flags ensure the final expect binary has no external dynamic dependencies.

4. Verify the standalone binary #

Navigate to the temporary install directory and check that the binary is truly independent:

ldd /tmp/expect-static/bin/expect

If you see output like not a dynamic executable or no system-level shared libraries listed, you've successfully built a static binary.

5. Integrate with your script #

• Copy the compiled expect binary from /tmp/expect-static/bin/ to your script's directory—for example, place it in a ./bin/ subfolder next to your main shell script.
• Update your shell script to call the local Expect binary instead of the system-wide one:

#!/bin/bash
# Get the directory where the script resides
SCRIPT_DIR=$(cd "$(dirname "${BASH_SOURCE[0]}")" &>/dev/null && pwd)
# Execute your Expect script using the local binary
"$SCRIPT_DIR/bin/expect" "$SCRIPT_DIR/your-expect-script.exp"

Key Notes #

• Cross-compiling for different architectures: If your target systems use a different CPU architecture (e.g., you're building on x86_64 for ARM devices), you'll need to use a cross-compilation toolchain. Add --host=your-target-arch (e.g., --host=arm-linux-gnueabihf) to the ./configure commands, and ensure your build environment has the appropriate cross-compiler installed.
• Stick to stable versions: Older, well-tested versions of Tcl and Expect are less likely to have compatibility issues on older target systems.
• Test thoroughly: Bundle your script and the Expect binary, then test on a target system to confirm everything runs without errors.

内容的提问来源于stack exchange，提问作者Jonathan Kittell