[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20040206: ldm6.0.14 at stc (cont.)

>From: "Anderson, Alan C. " <address@hidden>
>Organization: St. Cloud State
>Keywords: 200402061721.i16HLLp1027829 LDM configure install

Hi Alan,

>Thanks for prompt reply, but I am wondering
>about the failure statements near the end of my 
>config.log ?

Your config.log is the output of configure.  What configure does
is to try compiling little test programs to figure out what is
supported by your setup.  It uses compile failures to learn what
kinds of defines must be made in the C code to build successfully.
The really important log output is the stuff that gets written
to the screen when one runs configure, especially the end stuff.
Here is what you sent in:

creating cache ./config.cache
checking user-defined C compiler "/opt/SUNWspro/bin/cc"
checking C compiler... works
checking the installation prefix... /usr/local/ldm/ldm-6.0.14
checking domain name... stcloudstate.edu
checking how to run the C preprocessor... /opt/SUNWspro/bin/cc -E
checking for AIX... no
checking for HP-UX... no
checking whether memory-mapping by region is appropriate... no
checking the C preprocessor... works
checking for ar... ar
checking for perl... /bin/perl
checking for POSIX shell... /bin/sh
checking for yacc... yacc
checking for yacc library... 
checking for yyerror() in default library(s)... no
checking for yyerror() in -ly... yes
checking mmap()... yes
checking LDMHOME... /usr/local/ldm
checking size of int... 4
checking size of long... 4
checking for ANSI C header files... yes
checking for size_t... yes
checking for off_t... yes
checking for ssize_t... yes
checking for ptrdiff_t... yes
checking for socklen_t... yes
checking for stdlib.h... yes
checking for unistd.h... yes
checking for fsync... yes
checking for ftruncate... yes
checking for memmove... yes
checking for memcmp... yes
checking for rename... yes
checking for strerror... yes
checking for waitpid... yes
checking for strdup... yes
checking for seteuid... yes
checking for setenv... no
checking for mmap... yes
checking for sig_atomic_t in signal.h... defined
checking for working const... yes
checking for st_blksize in struct stat... yes
checking for sigaction... yes
checking RPC and socket references... -R/usr/ucblib -L/usr/ucblib -lrpcsoc 
-lnsl -lsocket
checking ulog defines... -D_DEV_CONSLOG
checking for gdbm_open in -lgdbm... no
configure: warning: GDBMLIB not set
checking for dbm_open... yes
checking for catman... catman
checking for manual-page index command... catman -w -M $(MANDIR)
updating cache ./config.cache
creating ./config.status
creating macros.make
creating pqbinstats/mailpqstats
creating scour/scour
creating scripts/ldmadmin
creating scripts/ldmprods
creating scripts/ldmfail
creating scripts/netcheck
creating scripts/syscheck
creating scripts/ldmcheck
creating config/ldmconfig.h

You see that this ends with no complaints.  If there had been anything
seriously wrong, you would have gotten an error message here and configure
would have terminated abnormally.  The end of your ./configure output
looks normal, so you can plunge in at this point and build the executables,
and then do the installs as per my previous email.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publically available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.