Bus Error during Solaris compile

[Chris Gill]

Hello all,
I keep thinking this should be a simple problem, but I've bashed my head
against it repeatedly to no avail. I'm trying to compile Nagios 1.1 on
Solaris 8, installed on an Ultra 5, with the most rescent patch cluster
installed. I'm using GCC 3.0, and I've been able to compile other software
just fine.
Any thoughts on how to fix this?

Thanks,

-Chris Gill

Here's the complete output:

# ./configure --with-gd-inc=/usr/local/include/ 
--with-gd-lib=/usr/local/lib
creating cache ./config.cache
checking for a BSD compatible install... /usr/local/bin/install -c
checking for gcc... gcc
checking whether the C compiler (gcc  ) works... yes
checking whether the C compiler (gcc  ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking whether make sets ${MAKE}... yes
checking for strip... /usr/ccs/bin/strip
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking whether time.h and sys/time.h may both be included... yes
checking for sys/wait.h that is POSIX.1 compatible... yes
checking for ctype.h... yes
checking for dirent.h... yes
checking for errno.h... yes
checking for fcntl.h... yes
checking for getopt.h... no
checking for grp.h... yes
checking for limits.h... yes
checking for math.h... yes
checking for pwd.h... yes
checking for signal.h... yes
checking for strings.h... yes
checking for string.h... yes
checking for syslog.h... yes
checking for unistd.h... yes
checking for uio.h... no
checking for sys/types.h... yes
checking for sys/time.h... yes
checking for sys/resource.h... yes
checking for sys/wait.h... (cached) yes
checking for sys/stat.h... yes
checking for sys/ipc.h... yes
checking for sys/msg.h... yes
checking for working const... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for tm_zone in struct tm... no
checking for tzname... yes
checking for mode_t... yes
checking for pid_t... yes
checking for size_t... yes
checking return type of signal handlers... void
checking for uid_t in sys/types.h... yes
checking type of array argument to getgroups... int
checking for strdup... yes
checking for strstr... yes
checking for strtoul... yes
checking for initgroups... yes
checking for type of socket size... size_t
checking for mail... /usr/bin/mail
Init script directory:  /etc/init.d
We'll use default routines (in xdata/xsddefault.*) for status data I/O...
We'll use default routines (in xdata/xcddefault.*) for comment data I/O...
We'll use template-based routines (in xdata/xedtemplate.*) for extended 
data I/O...
We'll use default routines (in xdata/xrddefault.*) for retention data 
I/O...
We'll use template-based routines (in xdata/xodtemplate.*) for object data 
I/O...
We'll use default routines (in xdata/xpddefault.*) for performance data 
I/O...
We'll use default routines (in xdata/xdddefault.*) for scheduled downtime 
data I/O...
checking for gdImagePng in -lgd (order 1)... yes
GD library was found!
checking for traceroute... /usr/sbin/traceroute
checking for snprintf... yes
checking for type va_list... yes
checking for perl... /usr/bin/perl
updating cache ./config.cache
creating ./config.status
creating Makefile
creating subst
creating pkginfo
creating base/Makefile
creating common/Makefile
creating contrib/Makefile
creating cgi/Makefile
creating html/Makefile
creating xdata/Makefile
creating daemon-init
creating html/index.html
creating html/side.html
creating common/config.h
creating common/snprintf.h
creating base/nagios.h
creating cgi/cgiutils.h

Creating sample config files in sample-config/ ...


*** Configuration summary for nagios 1.1 06-02-2003 ***:

 General Options:
 -------------------------
        Nagios executable:  nagios
        Nagios user/group:  nagios,nagios
       Command user/group:  nagios,nagios
            Embedded Perl:  no
        Install ${prefix}:  /usr/local/nagios
                Lock file:  ${prefix}/var/nagios.lock
           Init directory:  /etc/init.d

 Web Interface Options:
 ------------------------
                 HTML URL:  http://localhost/nagios/
                  CGI URL:  http://localhost/nagios/cgi-bin/
 Traceroute (used by WAP):  /usr/sbin/traceroute

 External Data Routines:
 ------------------------
              Status data:  Default (text file)
              Object data:  Template-based (text file)
             Comment data:  Default (text file)
            Downtime data:  Default (text file)
           Retention data:  Default (text file)
          Peformance data:  Default (external commands)
       Extended info data:  Template-based (text file)


Review the options above for accuracy.  If they look okay,
type 'make all' to compile the main program and CGIs.

# make
Please supply a command line argument (i.e. 'make all').  Other targets 
are:
   nagios cgis contrib
   clean
   install install-html install-config install-init install-commandmode 
fullinstall
# make nagios
cd ./base && make
gcc -g -O2 -I/usr/local/include/ -DHAVE_CONFIG_H -DNSCORE  -c  checks.c
checks.c: In function `run_service_check':
checks.c:506: Internal error: Bus Error
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
*** Error code 1
make: Fatal error: Command failed for target `checks.o'
Current working directory /usr/local/nagios-1.1/base
*** Error code 1
make: Fatal error: Command failed for target `nagios'
# 





-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null