Mit Scheme Installation Error in Ubuntu (Environment Variable Settings) - linux

I'm trying to install MIT-Scheme in Ubuntu on Windows 10.
I downloaded the tar-file from the Mit-Scheme website.
I run the command tar -xzf mit-scheme-9.2.tar.gz. Then cd mit-scheme-9.2/. Then cd src. Then ./configure.
However, I get the error logs below. Appreciate some advise. Thanks.
mingerz#DESKTOP-BMERQIM:~/mit-scheme-9.2/src$ ./configure
checking whether make sets $(MAKE)... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for native-code support... yes, for x86-64
checking for an existing MIT/GNU Scheme installation... configure: error:
This script needs an existing MIT/GNU Scheme installation to function,
but the following programs do not run it:
mit-scheme-x86-64
mit-scheme
If you have installed MIT/GNU Scheme in an unusual location, set the
environment variable MIT_SCHEME_EXE to the name or pathname of the
MIT/GNU Scheme executable, which is usually `mit-scheme' or
`/usr/local/bin/mit-scheme', and set the environment variable
MITSCHEME_LIBRARY_PATH to the pathname of the MIT/GNU Scheme library
directory, which is usually `/usr/local/lib/mit-scheme-x86-64'.
I dont understand how to implement the suggestion it is asking me to in regards to the environment variable.

This script needs an existing MIT/GNU Scheme installation to function
$ sudo apt-get install mit-scheme : http://packages.ubuntu.com/search?keywords=mit-scheme&searchon=names

Facing same issue on mac.
Instead of building from source, installing package helped in my case.
A. Installing Binary :
Get MIT-scheme (package) for Ubunto from MIT site http://www.gnu.org/software/mit-scheme/
Install it
Alias mit_scheme in ~/.bash_profile -->
alias mit-scheme=" path to MIT_scheme on your machine"
eg. alias mit-scheme="/Applications/MIT-Scheme.app/Contents/Resources/mit-scheme"
So that you can access it from bash.
B. If building from source, this link might be helpful.
https://groups.csail.mit.edu/mac/users/gjs/6.945/dont-panic/
And they say --> Don't Panic

Related

Build Pulseaudio-11.1 and intltool >= 0.35.0 bug

Im trying to build pulseaudio-11.1 because firefox asks for it to play audio on video.
Im using knoppix 8.1, 64 bit installation, but it runs in 32bits.
When I configure the pulseaudio source, I get a message stating that intltool is too old. Despite having met their version requirement at 0.35.0. I installed from source version 0.51.0 and 0.50.2 but neither installation satisfied the demand. I get the same message at the end when I run bootstrap.sh
root#kami:/Downloads/pulseaudio-11.1# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... //bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether UID '0' is supported by ustar format... yes
checking whether GID '0' is supported by ustar format... yes
checking how to create a ustar tar archive... gnutar
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for stow... no
checking whether make supports nested variables... (cached) yes
checking whether ln -s works... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports C++11 features by default... yes
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... //bin/grep
checking for egrep... //bin/grep -E
checking whether gcc needs -traditional... no
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking minix/config.h usability... no
checking minix/config.h presence... no
checking for minix/config.h... no
checking whether it is safe to define __EXTENSIONS__... yes
checking for gm4... no
checking for m4... m4
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking whether NLS is requested... yes
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in m/^(.*)\${ <-- HERE ?([A-Z_]+)}?(.*)$/ at /usr/local/bin/intltool-update line 1064.
checking for intltool >= 0.35.0... found
configure: error: Your intltool is too old. You need intltool 0.35.0 or later.
This was before and after I removed version 0.35.0 of intltool that was pre-installed and then installed the newer versions, 0.51.0, then 0.50.2 to try a slightly older version if there was something wrong with the newest release, which is ironically quite old dating back to 2015.
Also bizarrly to top it off as you can see in the output before stating that the version is too old that it had found exactly what it is saying it does not have.
So in conclusion pulseaudio asks for intltool >= 0.35.0 which it finds and says right afterwards that it has not, which remained true across 3 seperate instances that satisfied their request on version 0.35.0, 0.51.0 and 0.50.2
Any help is appreciated.
At installation 'NetworkManager-l2tp-master' i stumbled upon an error:
configure: error: Your intltool is too old. You need intltool 0.35 or later.
I used intermediate commands:
./configure
sudo apt update
sudo apt install intltool imagemagick libmagickcore-dev pstoedit libpstoedit-dev
git clone https://github.com/autotrace/autotrace.git
cd autotrace
#unnecessary command for clarification should bugs be introduced later
git rev-parse HEAD
#t86c9c80c4h669302cb2571c0cab0rer7a102731
./autogen.sh
cd .. # necessarily exit from 'autotrace' directory
autoreconf -i
./configure # again
after that, the error is resolved and indicates to:
configure: error: Package requirements (gtk+-3.0 >= 3.4) were not met:
No package 'gtk+-3.0' found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables GTK_CFLAGS
and GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
This alert indicates that possible it is not installed pkg-config (corresponding version of Linux).

Wine Cannot build a 32-bit program error

So I've been getting this problem (as seen below) on my CentOS 7 (64-bit) server when I try and configure wine with png with the following code:
./configure --with-png
I need this to run a specific server for a game called Mount & Blade Warband.
Because when I run the server i get this:
err:wincodecs:PngEncoder_CreateInstance Trying to save PNG picture, but PNG support is not compiled in.
fixme:ole:CoCreateInstance no instance created for interface {00000103-a8f2-4877-ba0a-fd2b6645fb94} of class {27949969-876a-41d7-9447-568f6a35a4dc}, hres is 0x80004005
I have looked at this post:
https://www.centos.org/forums/viewtopic.php?f=13&t=44897
They said that the following code should fix it:
yum install glibc-devel.i686
But it didn't, atleast not for me. I`m still getting the following error over and over:
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for cpp... cpp
checking for ld... ld
checking whether gcc -m32 works... no
configure: error: Cannot build a 32-bit program, you need to install 32-bit development libraries.
Solved, I had to run this code to install 32-bit devolpment libraries in order to do --with-png. The code came from this post:
https://www.centos.org/forums/viewtopic.php?f=48&t=49542
Code:
yum install glibc-devel.i686 dbus-devel.i686 freetype-devel.i686 pulseaudio- libs-devel.i686 libX11-devel.i686 mesa-libGLU-devel.i686 libICE-devel.i686 libXext-devel.i686 libXcursor-devel.i686 libXi-devel.i686 libXxf86vm-devel.i686 libXrender-devel.i686 libXinerama-devel.i686 libXcomposite-devel.i686 libXrandr-devel.i686 mesa-libGL-devel.i686 mesa-libOSMesa-devel.i686 libxml2-devel.i686 libxslt-devel.i686 zlib-devel.i686 gnutls-devel.i686 ncurses-devel.i686 sane-backends-devel.i686 libv4l-devel.i686 libgphoto2-devel.i686 libexif-devel.i686 lcms2-devel.i686 gettext-devel.i686 isdn4k-utils-devel.i686 cups-devel.i686 fontconfig-devel.i686 gsm-devel.i686 libjpeg-turbo-devel.i686 pkgconfig.i686 libtiff-devel.i686 unixODBC.i686 openldap-devel.i686 alsa-lib-devel.i686 audiofile-devel.i686 freeglut-devel.i686 giflib-devel.i686 gstreamer-devel.i686 gstreamer-plugins-base-devel.i686 libXmu-devel.i686 libXxf86dga-devel.i686 libieee1284-devel.i686 libpng-devel.i686 librsvg2-devel.i686 libstdc++-devel.i686 libusb-devel.i686 unixODBC-devel.i686 qt-devel.i686

Configure fail when build the pam_sasl module

I downloaded pam_sasl source code from
http://sourceforge.net/projects/pam-sasl/?source=typ_redirect
After issue ./configure command, it returns configure: error: sasl2 not found
linux-xbx0:~/pam_sasl-0.1.2 # ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for xsltproc... /usr/bin/xsltproc
checking for sasl_checkpass in -lsasl2... no
configure: error: sasl2 not found
linux-xbx0:~/pam_sasl-0.1.2 # rpm -ql libsasl2-3-2.1.26-7.1.x86_64
/usr/lib64/libsasl2.so.3
/usr/lib64/libsasl2.so.3.0.0
linux-xbx0:~/pam_sasl-0.1.2 # echo $LD_LIBRARY_PATH
:/usr/lib:/usr/lib64:/usr/lib:/usr/lib64:/usr/lib/sasl2/:/usr/lib64/sasl2
linux-xbx0:~/pam_sasl-0.1.2 # rpm -qa | grep sasl
cyrus-sasl-sqlauxprop-32bit-2.1.26-7.1.x86_64
cyrus-sasl-gssapi-2.1.26-7.1.x86_64
libsasl2-3-2.1.26-7.1.x86_64
libsasl2-3-32bit-2.1.26-7.1.x86_64
cyrus-sasl-saslauthd-2.1.26-7.1.x86_64
cyrus-sasl-crammd5-2.1.26-7.1.x86_64
cyrus-sasl-otp-2.1.26-7.1.x86_64
cyrus-sasl-32bit-2.1.26-7.1.x86_64
cyrus-sasl-digestmd5-2.1.26-7.1.x86_64
cyrus-sasl-gssapi-32bit-2.1.26-7.1.x86_64
cyrus-sasl-plain-32bit-2.1.26-7.1.x86_64
cyrus-sasl-sqlauxprop-2.1.26-7.1.x86_64
cyrus-sasl-plain-2.1.26-7.1.x86_64
cyrus-sasl-otp-32bit-2.1.26-7.1.x86_64
cyrus-sasl-2.1.26-7.1.x86_64
cyrus-sasl-crammd5-32bit-2.1.26-7.1.x86_64
linux-xbx0:~/pam_sasl-0.1.2 # cat /etc/*release
SUSE Linux Enterprise Server 12 (x86_64) VERSION = 12 PATCHLEVEL = 1
Development packages corresponding to the "normal" packages usually have a -devel appended to their name. Since the SASL2 library is provided by the package cyrus-sasl you are now looking for the package cyrus-sasl-devel.
Since you are using an openSUSE distribution derivate, here SLES, you can use either the provided software management utility, YaST to install that package, or the command line tool zypper if installed, which is much faster in use. So you have these two alternatives:
launch the YaST control center, chose the "Software Management" module, wait until it is loaded. Then search for the string "sasl" and pick the package from the list of hits.
zypper install cyrus-sasl-devel

Configure options for building MinGW-64 on linux-64 for linux-64 (ultimately targetting windows-64)

I want to build MinGW-w64 where:
A: I want to compile MinGW itself on Linux (64-bit).
B: I want the MinGW tools (compiler, etc) to run on Linux (64-bit).
C: I want the MinGW tools (compiler, etc) to produce code that runs on Windows 64-bit (Win7 & Win8).
I'm having trouble at the configure stage. I've googled around a bit but I can't find out what options I need to pass to configure.
I have downloaded the source for MinGW-w64 SVN from (https://svn.code.sf.net/p/mingw-w64/code/trunk/).
(AFAICT this is the current official repo).
The source has a text help (mingw-w64-doc/howto-build/mingw-w64-howto-build.txt). However, this is primarily intended for those wanting to run MinGW tools on Windows.
The example options (for a non-multilib w64 target) are: --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 --disable-multilib
But I think I want the host option to refer to linux (right?). I've tried --host=x86_64-linux-gnuand --host=x86_64-pc-linux-gnu but no luck.
I get the error:
configure: error: Please check if the mingw-w64 header set and the build/host option are set properly.
configure: error: ../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-crt/configure failed for mingw-w64-crt
The full log is
checking whether to enable maintainer-specific portions of Makefiles... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/make/tool/MinGW/svn/mingw-w64-v6615-2014-05-07/build-aux/missing: Unknown `--is-lightweight' option
Try `/make/tool/MinGW/svn/mingw-w64-v6615-2014-05-07/build-aux/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for x86_64-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking whether to build the headers... yes
checking whether to build the crt... yes
checking whether to build the optional libraries... no
checking whether to build the optional tools... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating config.h
config.status: config.h is unchanged
=== configuring in mingw-w64-headers (/make/tool/MinGW/build/v6615-2014-05-07/mingw-w64-headers)
configure: running /bin/bash ../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-headers/configure --disable-option-checking '--prefix=/make/tool/MinGW/use/v6615/x86_64-w64-mingw32' '--target=x86_64-w64-mingw32' '--host=x86_64-linux-gnu' '--disable-multilib' '--with-sysroot=/make/tool/MinGW/use/v6615/x86_64-w64-mingw32' 'host_alias=x86_64-linux-gnu' 'target_alias=x86_64-w64-mingw32' --cache-file=/dev/null --srcdir=../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-headers
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
/make/tool/MinGW/svn/mingw-w64-v6615-2014-05-07/mingw-w64-headers/build-aux/missing: Unknown `--is-lightweight' option
Try `/make/tool/MinGW/svn/mingw-w64-v6615-2014-05-07/mingw-w64-headers/build-aux/missing --help' for more information
configure: WARNING: 'missing' script is too old or missing
checking for x86_64-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking whether to rebuild headers with widl... no
checking whether to build a w32api package for Cygwin... no
checking for c-runtime headers... yes
checking for optional sdk headers... ddk,directx
checking if installing idl files is enabled... no
checking whether to enable the secure API... no
checking that generated files are newer than configure... done
configure: creating ./config.status
config.status: creating Makefile
config.status: creating crt/_mingw.h
config.status: creating config.h
config.status: config.h is unchanged
=== configuring in mingw-w64-crt (/make/tool/MinGW/build/v6615-2014-05-07/mingw-w64-crt)
configure: running /bin/bash ../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-crt/configure --disable-option-checking '--prefix=/make/tool/MinGW/use/v6615/x86_64-w64-mingw32' '--target=x86_64-w64-mingw32' '--host=x86_64-linux-gnu' '--disable-multilib' '--with-sysroot=/make/tool/MinGW/use/v6615/x86_64-w64-mingw32' 'host_alias=x86_64-linux-gnu' 'target_alias=x86_64-w64-mingw32' --cache-file=/dev/null --srcdir=../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-crt
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for x86_64-linux-gnu-strip... no
checking for strip... strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for sysroot... /make/tool/MinGW/use/v6615/x86_64-w64-mingw32
checking for a sed that does not truncate output... /bin/sed
checking for gawk... (cached) gawk
checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-linux-gnu-gcc accepts -g... yes
checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
checking whether x86_64-linux-gnu-gcc understands -c and -o together... yes
checking for style of include used by make... GNU
checking dependency style of x86_64-linux-gnu-gcc... gcc3
checking for x86_64-linux-gnu-g++... x86_64-linux-gnu-g++
checking whether we are using the GNU C++ compiler... yes
checking whether x86_64-linux-gnu-g++ accepts -g... yes
checking dependency style of x86_64-linux-gnu-g++... gcc3
checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
checking for x86_64-linux-gnu-ranlib... no
checking for ranlib... ranlib
checking for x86_64-linux-gnu-dlltool... no
checking for dlltool... no
checking for x86_64-linux-gnu-ar... no
checking for x86_64-linux-gnu-lib... no
checking for x86_64-linux-gnu-link... no
checking for ar... ar
checking the archiver (ar) interface... ar
checking dependency style of x86_64-linux-gnu-gcc... gcc3
checking for x86_64-linux-gnu-as... no
checking for as... as
checking whether to build a w32api package for Cygwin... no
checking whether to build the Win32 libraries... no
checking whether to build the Win64 libraries... yes
checking whether to build the WinCE libraries... no
checking whether to enable globbing... no
checking whether to enable private exports... no
checking whether to enable delay import libs... no
checking whether to enable experimental features... no
checking whether the compiler supports -municode... no
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking _mingw_mac.h usability... no
checking _mingw_mac.h presence... no
checking for _mingw_mac.h... no
configure: error: Please check if the mingw-w64 header set and the build/host option are set properly.
configure: error: ../../../svn/mingw-w64-v6615-2014-05-07/mingw-w64-crt/configure failed for mingw-w64-crt
NOTE: I can successfully compile native GCC & Clang from source.
Purpose:
My ultimate goal is to use the latest Clang to produce C++14 code for Windows 7/8 64-bit (including D3D11 & OpenGL).
I want to build trunk MinGW because the latest Clang produces assembly code that the default MinGW cannot assemble (mainly "junk at end of line" errors).
As of 2014-05-07 (today), only Clang offers full C++14 support, and I am making use of features only available in Clang (eg: variable templates).
Yet, Clang relies on GCC / MinGW for assembling and linking.
Info:
OS: Linux Mint 16 64-bit (XFCE).
Thanks for all assistance.
Old question, but an answer might be helpful to those coming from google.
The host and build flags are a bit misleading. The info from the help page at mingw-w64-crt/configure --help shows:
System types:
--build=BUILD configure for building on BUILD [guessed]
--host=HOST cross-compile to build programs to run on HOST [BUILD]
So we want to leave --build alone, and specify the windows system we wish to cross-compile for with --host.
So, the way to build for 64bit windows, and include both 32bit and 64bit libraries and std::experimental features is with:
./configure --enable-lib32 --enable-lib64 --enable-experimental --host=x86_64-w64-mingw32
It's very similar if you want to build for 32bit windows, but of course you can't enable 64bit mode:
./configure --enable-lib32 --enable-experimental --host=i686-w64-mingw32
https://github.com/Zeranoe/mingw-w64-build
I think your answer is here:
./mingw-w64-build x86_64 for 64bit;
or
./mingw-w64-build x86_64 i686 for 32bit.
I met the same error while configuring. After reading the shell in mingw-w64-build this file, I think you will have to execute:
./configure in folder ../x86_64-w64-v8.0.0/mingw-w64-headers,
then
./configure in folder ../x86_64-w64-v8.0.0/mingw-w64-crt,
and finally
./configure in folder ../x86_64-w64-v8.0.0/mingw-w64-libraries/winpthreads.
I did not verify the whole process manually, because this shell file just did the job.
Maybe you could try this - its the latest version of mingw and you dont have to compile it by yourself:
https://github.com/Zeranoe/mingw-w64-build
it supports almost all distros...

Cross Compiling Expect for ARM

I have downloaded expect5.4 . I'm trying to cross compile it for ARM(PandaBoard) running stripped down version of linux.
In the initial setup of configuring , I try
Shell$ ./configure --host=ARM
configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.
checking for correct TEA configuration... ok (TEA 3.9)
configure: configuring expect 5.45
checking for Tcl configuration... found /home/user1/scripts/tcl8.6.0/unix/tclConfig.sh
checking for existence of /home/user1/scripts/tcl8.6.0/unix/tclConfig.sh... loading
configure: --prefix defaulting to TCL_PREFIX /usr/local
configure: --exec-prefix defaulting to TCL_EXEC_PREFIX /usr/local
checking for ARM-gcc... /home/user1/toolchain/toolchain/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... yes
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether /home/user1/toolchain/toolchain/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc accepts -g... yes
checking for /home/user1/toolchain/toolchain/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... /home/user1/toolchain/toolchain/arm-none-linux-gnueabi/bin/arm-none-linux-gnueabi-gcc -E
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... yes
checking for ARM-ranlib... no
checking for ranlib... ranlib
checking for egrep... grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
..
..
..
..
..
checking for openpty... no
checking for openpty in -lutil... yes
checking if running Sequent running SVR4... no
checking build system type... i686-pc-linux-gnu
checking host system type... Invalid configuration `ARM': machine `ARM' not recognized
configure: error: /bin/bash tclconfig/config.sub ARM failed
UPDATE:
On compiling with ./configure --host=arm , It goes further the error i'm getting now is
checking for sysconf... yes
checking for strftime... yes
checking for strchr... yes
checking for timezone... yes
checking for siglongjmp... yes
checking for memcpy... yes
checking if WNOHANG requires _POSIX_SOURCE... configure: error: Expect can't be cross compiled
Its able to pick arm-gcc but it fails for some reason.
You will get a bit further with --host=arm (lowercase), but not
much: expect just doesn't want to be cross-compiled. Overcoming this
would require non-trivial modifications in configure.in. It could be
rational to work on them if expect is the only thing you want to
cross-compile, but if there are many others, you'd better setup some
environment where you can run compiled binaries (scratchbox or
something like that).
Expect (Version = 5.45.4) is available in buildroot 2019.11 and it has support for the PandaBoard.
You could
download `buildroot 2019.11' from the project .
Extract it
run make pandaboard_defconfig inside the buildroot-folder
run make menuconfig and enable TCL(-> Target packages
-> Interpreter languages and scripting) and then expect (-> Target packages
-> Interpreter languages and scripting) because of the dependency
run make to build the whole thing and get the executable from the
output/build/expect folder

Resources