Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

problems with autoconf

Programming languages, Coding, Executables, Package Creation, and Scripting.
Post Reply
Message
Author
Ulli
Posts: 1
Joined: 2015-12-30 14:29

problems with autoconf

#1 Post by Ulli »

I would like to write my own autoconf file using Debian Lenny.

I generate the first version with autoscan.

For that I switch into the source directory and type:
autoscan

This generates a file called configure.scan which looks like this:

# -*- Autoconf -*-
# Process this file with autoconf to produce a configure script.

AC_PREREQ([2.69])
AC_INIT([FULL-PACKAGE-NAME], [VERSION], [BUG-REPORT-ADDRESS])
AC_CONFIG_SRCDIR([utils.h])
AC_CONFIG_HEADERS([config.h])

# Checks for programs.
AC_PROG_CXX
AC_PROG_AWK
AC_PROG_CC
AC_PROG_CPP
AC_PROG_INSTALL
AC_PROG_LN_S
AC_PROG_MAKE_SET
AC_PROG_RANLIB

# Checks for libraries.
# FIXME: Replace `main' with a function in `-lann':
AC_CHECK_LIB([ann], [main])

# Checks for header files.
AC_CHECK_HEADERS([stdlib.h string.h sys/time.h])

# Checks for typedefs, structures, and compiler characteristics.
AC_CHECK_HEADER_STDBOOL

# Checks for library functions.

AC_CONFIG_FILES([Makefile])
AC_OUTPUT



Now i rename this file to configure.ac

and type:

aclocal
autoconf
./configure

and get the following error message.

configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."

Isn't autoscan supposed to create a working configure script ?

corutils and shtool are installed.

Thanks for any help.


-----------------------

Ulli

tomazzi
Posts: 730
Joined: 2013-08-02 21:33

Re: problems with autoconf

#2 Post by tomazzi »

Hi, this is a classic problem ;)
Most of beginners are having problems with proper usage of the autotools toolchains, but fortunately there is an excellent tool called: "autoreconf".
Autoreconf generally provides ways to check the correctness of project configuration, but in Your case the most important thing is, that It can install missing files.

Code: Select all

autoreconf -i
It's also a good idea to let it reparse the whole project, especially if You have just started with autotools:

Code: Select all

autoreconf -f
In fact, those missing files could be simply copied to the project dir, but this is not recommended - there may be issues with different versions, especially if one will try to download those files from the internet.

Regards.
Odi profanum vulgus

User avatar
GarryRicketson
Posts: 5644
Joined: 2015-01-20 22:16
Location: Durango, Mexico

Re: problems with autoconf

#3 Post by GarryRicketson »

I don't know if this will be any use to the OP, it might be,
It is more intended for Debian packagers, anyway, here it is:

https://www.debian.org/doc/manuals/deve ... -autotools
6.7.1. Packages using autoconf/automake
Keeping autoconf's config.sub and config.guess files up to date is critical for porters, especially on more volatile architectures. Some very good packaging practices for any package using autoconf and/or automake have been synthesized in /usr/share/doc/autotools-dev/README.Debian.gz from the autotools-dev package. You're strongly encouraged to read this file and to follow the given recommendations.
It might be worth the effort to open this up, and read it,

Code: Select all

/usr/share/doc/autotools-dev/README.Debian.gz
(if Debian Lenny has it), I do have it on "wheezy"
--------------------------
Here is another:
http://www.sourceware.org/autobook/auto ... k_toc.html

Post Reply