Autoconf

[Ryan C. Gordon]

> Please note: you probably do *not* want to add these files to CVS
> (they should be generated by the bootstrap script):
>   config.guess, config.sub, configure, depcomp, install-sh, ltconfi,
> ltmain.sh, missing, mkinstalldirs

I am supposed to be running the "bootstrap" script, which then prepares
./configure to be run, right? After ./configure succeeds, I can run make.
Is that correct?

This is the output I'm getting...

[icculus at gemini ~/2/SDL_sound_mod]$ ./bootstrap
aclocal: configure.in: 65: macro `AM_PATH_SDL' not found in library
aclocal: configure.in: 78: macro `AM_PATH_LIBMIKMOD' not found in library
aclocal: configure.in: 92: macro `AM_PATH_VORBIS' not found in library
aclocal: configure.in: 106: macro `AM_PATH_SMPEG' not found in library
automake: unrecognized option -- `--force'
Try `automake --help' for more information.
autoconf: Undefined macros:
configure.in:125:AC_FUNC_MALLOC

(Although it's good to note that the configure script gets created, but
unless I have the pregenerated install-sh in the SDL_sound root directory,
I get this when running configure:

[icculus at gemini ~/projects/SDL_sound]$ ./configure
loading cache ./config.cache
configure: error: can not find install-sh or install.sh in . ./.. ./../..


With install-sh in place, configure mostly works, with some caveats:
/home/icculus/projects/SDL_sound/missing:
/home/icculus/projects/SDL_sound/missing: No such file or directory
configure: warning: `missing' script is too old or missing
(...later in the output...)
./configure: AC_FUNC_MALLOC: command not found

Still, the configure runs through, and "make" produces:
[icculus at gemini ~/projects/SDL_sound]$ make
make: *** No rule to make target `Makefile.am', needed by `Makefile.in'.
Stop.


So that we're working from the same tree, I've checked in what should be
in CVS according to the list (i.e. everything but config.guess, etc...)

I assume that the first couple iterations of the autoconf scripts will
need a lot of smoothing out until they've been tried on a few platforms
(and different distributions of the same platform). On the other hand, I
won't rule out that I've simply screwed something up.

Let me know.

--ryan.