>Is it a bad assumption to think that amanda's build process will >"bail" if there is something that it needs which is not found by the >configure/autoconf programs?
It's not a bad assumption. Whether it does actually bail or not is a different question :-). In other words, if it doesn't, it's probably a bug that needs to be fixed. >checking for working aclocal... missing >checking for working autoconf... missing >checking for working automake... missing >checking for working autoheader... missing >checking for working makeinfo... missing None of these are required for building Amanda from a tarball. Note that some of the tests ./configure runs come from autoconf all on its own. For instance, there isn't anything in the Amanda configure.in that hunts for aclocal (or autoconf, etc). We "inherit" those tests from something else autoconf throws in. >checking for bison... no >checking for byacc... no These are OK if your system comes with vendor versions of yacc and lex. Even then, the Amanda tarball comes with the .c files corresponding to the .y/.l ones, so unless you make changes you probably don't even need yacc/lex (or their GNU equivalents). >checking for perl5... no > > [Note perl 5.005 is at /usr/bin/perl... > whereis finds it no problem... > /usr/bin is in my path Don't know why this happened. There should be more in config.log. >checking for yywrap in -lfl... no > > > [Note: I have installed the GNU flex-2.5.4 > thinking the yywrap would be included... > The fl library file is where I expect. Ditto. >checking for history.h... no >checking for readline.h... no >checking for readline/history.h... no >checking for readline/readline.h... no > > [Note: These are installed and accessible. > Why not found ?? Ditto. And another idea. What happens with many of these tests is that a little bit of C code is generated and then the compiler is run, sometimes just to compile, sometimes to also link, and occasionally to actually run the resulting test program. If there is something basic wrong with your compiler (for instance, it requires a license and anything you do generates an error), ./configure is going to say lots of things were not found when what it really means is the test failed for some other reason. Not saying that's what's going on with your setup, but it's happened more than once. >-J John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
