>I have searched the config.log file and I see no references to the
>string 'ruserok' with regard to the "multiply declared ruserok"
>issue...
That doesn't make any sense. Here's what I see:
configure:14463: checking for ruserok
configure:14491: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include -L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
configure:14517: checking for ruserok declaration in netdb.h sys/socket.h libc.h
and so on. In other words, every place ./configure does a test
there should be the same thing in the log along with the actual test
and results. Here's a failure, for instance (Solaris does not have
setmntent):
configure:15096: checking for setmntent
configure:15124: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include -L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
Undefined first referenced
symbol in file
setmntent /var/tmp/cccfHbIc.o
ld: fatal: Symbol referencing errors. No output written to conftest
collect2: ld returned 1 exit status
configure: failed program was:
#line 15101 "configure"
#include "confdefs.h"
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char setmntent(); below. */
#include <assert.h>
/* Override any gcc2 internal prototype to avoid an error. */
/* We use char because int might match the return type of a gcc2
builtin and then its argument prototype would still apply. */
char setmntent();
int main() {
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined (__stub_setmntent) || defined (__stub___setmntent)
choke me
#else
setmntent();
#endif
; return 0; }
You have to do a "make distclean" first or else the stuff will come from
the cache and you won't see the test results.
>I see no reference to the flock tests or any lock tests for that
>matter... The only occurrence of the string 'lock' in the config.log
>file was inside the word 'block'
Again, this make no sense. Here's the very end of my log:
configure:19342: checking whether posix fcntl locking works
configure:19362: gcc -Wall -DPUCC -o conftest -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -g -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/opt/readline/include -I/opt/flex/include -L/opt/readline/lib -L/opt/flex/lib
-L/usr/local/lib conftest.c -lgen -lm -lreadline -ltermcap -lsocket -lnsl -lintl
1>&5
In file included from configure:19358:
/home/fortress/a/jrj/work/amanda/amanda-242/common-src/amflock.c:412: warning:
return-type defaults to `int'
If you're not seeing output like this (and you've done a distclean),
I'm not sure what's going on.
>CFLAGS="-I/usr/local/include" \
>LD_LIBRARY_PATH="/usr/local/lib:$LD_LIBRARY_PATH" \
>./configure \
>...
Setting LD_LIBRARY_PATH should be a last resort. I think you should be
able to accomplish the same thing setting LIBS, e.g.:
CFLAGS="-I/usr/local/include" \
LIBS="-L/usr/local/lib" \
./configure \
...
Then you need to look at the configure output to see what it says about
finding readline, e.g. from my system:
checking for readline.h... no
checking for readline/history.h... yes
checking for readline/readline.h... yes
checking for readline in -lreadline... yes
If that doesn't work, you're back to looking at config.log to find out
why the test programs failed.
>--with-debug-days=1
Any particular reason you're lowering this value? I'd think you'd want
at least a weekend worth of logs left around.
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
