[SOLVED] Need to compile ima-evm-utils, but the 'configure' script is not part of the package... don't know where to start.

accrig · 04-18-2016, 09:53 AM

I've compiled lots of programs from source, just run the configure script, then make, finally install. The instructions appear to be copypasted but I don't know where from.

In this case, the configure script does not exist in the tarball. (I downloaded it from the official project SF site: https://sourceforge.net/projects/lin...ar.gz/download). There is, however, a file named 'configure.ac'.

Am I supposed to be using autoconf? If so, can you point me to a document explaining where to start for a first-time autoconf user?

I'm trying to compile on raspbian, obviously for a raspberry pi. (Yes, I have gcc, make, etc. installed and no problem to compile other programs).

bat999 · 04-18-2016, 10:19 AM

Quote:

Originally Posted by accrig

... Am I supposed to be using autoconf?...

Hi
Inside the ima-evm-utils folder is a bash script "autogen.sh", you need to run that first.
It runs autoconf program for you to create the configure file.

Code:

$ cd ima-evm-utils-1.0
$ ./autogen.sh
$ ./configure
$ make

accrig · 04-18-2016, 10:29 AM

Thanks, that was a useful tip and I moved ahead a bit. There were some errors, though:

Code:

configure.ac:17: error: possibly undefined macro: AC_PROG_LIBTOOL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
pi@raspberrypi ~/ima-evm-utils-1.0 $ ./configure 
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."

I followed the tips in this thread so the files it was looking for were created, but it is still missing 'Makefile.in'.

Code:

pi@raspberrypi ~/ima-evm-utils-1.0 $ ./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... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking build system type... armv6l-unknown-linux-gnueabihf
checking host system type... armv6l-unknown-linux-gnueabihf
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 whether gcc and cc understand -c and -o together... yes
./configure: line 3748: AC_PROG_LIBTOOL: command not found
./configure: line 3750: LT_INIT: command not found
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 pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for OPENSSL... 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 unistd.h... (cached) yes
checking openssl/conf.h usability... yes
checking openssl/conf.h presence... yes
checking for openssl/conf.h... yes
checking attr/xattr.h usability... yes
checking attr/xattr.h presence... yes
checking for attr/xattr.h... yes
checking keyutils.h usability... yes
checking keyutils.h presence... yes
checking for keyutils.h... yes
checking whether to enable debug... yes
configure: creating ./config.status
config.status: error: cannot find input file: `Makefile.in'

Do you know where that file is supposed to be generated from?

accrig · 04-18-2016, 10:45 AM

Never mind, solved it by installing libtool (it appeared to be a macro name, I wouldn't have thought it was a package

).

Thanks for the useful answer.