[vox-tech] using autoconf (getting closer...)

[Peter Jay Salzman]

hi dave,

THANK YOU for replying!   i figured out what was going wrong.  i wrote a
hello world program:

#include<stdio.h>
int main(void)
{
   printf("hi\n");
   return 0;
}

with a simple make file:

hello: hello.c

and it STILL didn't work.   i began to poke around, and found that
the autoconf 2.5x and 2.13 debian packages were both installed on my
system.  apparently, they don't conflict with each other.

i made sure to use only the 2.5x tools, and lo and behold:

% autoscan 
% mv configure.scan configure.in 
% autoheader
autoheader: `config.h.in' is unchanged
% autoconf
% ./configure 
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
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 ANSI C... none needed
configure: error: cannot find install-sh or install.sh in . ./.. ./../..


woo hoo!  huge progress (i also uninstalled autoconf2.13).

of course, /usr/bin/install is on my system so the configure error is
troubling.   according to the autoconf info page:

- Macro: AC_PROG_INSTALL

     Set output variable `INSTALL' to the path of a BSD compatible
     `install' program, if one is found in the current `PATH'.
     Otherwise, set `INSTALL' to `DIR/install-sh -c', checking the
     directories specified to `AC_CONFIG_AUX_DIR' (or its default
     directories) to determine DIR (*note Output::).

which is odd, since /usr/bin is in my PATH.  the info page also says
that AC_PROG_INSTALL filters out "install" implementations that are
known to be buggy.

i doubt GNU install is buggy.

when the man page talks about PATH, it's talking about a shell variable,
right?  not some autoconf, make or configure variable?

any ideas?

pete


begin Dave Peticolas <dave@krondo.com> 
> On Wed, 2002-10-23 at 10:06, Peter Jay Salzman wrote:
> > hi dave,
> > 
> > ok, i'm now writing this knowing a bit more about autoconf than i did
> > yesterday.
> > 
> > do you mean that i should do something like:
> > 
> >    aclocal && autoheader && autoconf
> > 
> > the docs say that aclocal should output a file named something like
> > aclocal.m4 (or something like that) which is used with configure.in and
> > autoconf to generate a configure script.
> > 
> > however, aclocal isn't producing any files or output.
> 
> So aclocal isn't even giving an error message?
> 
> dave
> 



-- 
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D