Jessi151 Geschrieben 25. November 2004 Teilen Geschrieben 25. November 2004 Und zwar bekomme ich beim kompilieren von Nagios folgende Ausgabe: loading cache ./config.cache checking for a BSD compatible install... (cached) /usr/bin/install -c checking for gcc... (cached) 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... (cached) yes checking whether gcc accepts -g... (cached) yes checking whether make sets ${MAKE}... (cached) yes checking for strip... (cached) /usr/bin/strip checking how to run the C preprocessor... (cached) gcc -E checking for ANSI C header files... (cached) yes checking whether time.h and sys/time.h may both be included... (cached) yes checking for sys/wait.h that is POSIX.1 compatible... (cached) yes checking for ctype.h... (cached) yes checking for dirent.h... (cached) yes checking for errno.h... (cached) yes checking for fcntl.h... (cached) yes checking for getopt.h... (cached) yes checking for grp.h... (cached) yes checking for limits.h... (cached) yes checking for math.h... (cached) yes checking for pwd.h... (cached) yes checking for signal.h... (cached) yes checking for strings.h... (cached) yes checking for string.h... (cached) yes checking for syslog.h... (cached) yes checking for unistd.h... (cached) yes checking for uio.h... (cached) no checking for sys/types.h... (cached) yes checking for sys/time.h... (cached) yes checking for sys/resource.h... (cached) yes checking for sys/wait.h... (cached) yes checking for sys/stat.h... (cached) yes checking for sys/ipc.h... (cached) yes checking for sys/msg.h... (cached) yes checking for working const... (cached) yes checking whether struct tm is in sys/time.h or time.h... (cached) time.h checking for tm_zone in struct tm... (cached) yes checking for mode_t... (cached) yes checking for pid_t... (cached) yes checking for size_t... (cached) yes checking return type of signal handlers... (cached) void checking for uid_t in sys/types.h... (cached) yes checking type of array argument to getgroups... (cached) gid_t checking for strdup... (cached) yes checking for strstr... (cached) yes checking for strtoul... (cached) yes checking for initgroups... (cached) yes checking for type of socket size... size_t checking for mail... (cached) /usr/bin/mail Init script directory: /etc/rc.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 main in -liconv... (cached) no checking for gdImagePng in -lgd (order 1)... (cached) no checking for gdImagePng in -lgd (order 2)... (cached) no checking for gdImagePng in -lgd (order 3)... (cached) no *** GD, PNG, and/or JPEG libraries could not be located... ********* Boutell's GD library is required to compile the statusmap, trends and histogram CGIs. Get it from http://www.boutell.com/gd/, compile it, and use the --with-gd-lib and --with-gd-inc arguments to specify the locations of the GD library and include files. NOTE: In addition to the gd-devel library, you'll also need to make sure you have the png-devel and jpeg-devel libraries installed on your system. NOTE: After you install the necessary libraries on your system: 1. Make sure /etc/ld.so.conf has an entry for the directory in which the GD, PNG, and JPEG libraries are installed. 2. Run 'ldconfig' to update the run-time linker options. 3. Run 'make clean' in the Nagios distribution to clean out any old references to your previous compile. 4. Rerun the configure script. NOTE: If you can't get the configure script to recognize the GD libs on your system, get over it and move on to other things. The CGIs that use the GD libs are just a small part of the entire Nagios package. Get everything else working first and then revisit the problem. Make sure to check the nagios-users mailing list archives for possible solutions to GD library problems when you resume your troubleshooting. ******************************************************************** checking for traceroute... (cached) /usr/sbin/traceroute checking for snprintf... (cached) yes checking for type va_list... yes checking for perl... (cached) /usr/bin/perl 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 common/config.h is unchanged creating common/snprintf.h common/snprintf.h is unchanged creating base/nagios.h creating cgi/cgiutils.h cgi/cgiutils.h is unchanged Creating sample config files in sample-config/ ... *** Configuration summary for nagios 1.2 02-02-2004 ***: 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/rc.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. Was will er von mir? soll ich etwa das von der Website nstallieren? hab ich schon prob, da will er auch was für haben. Alle Komponente, die yast unter der Eingabe von gd findet, hab ich schon installiert... Wäre dringend thx Zitieren Link zu diesem Kommentar Auf anderen Seiten teilen Mehr Optionen zum Teilen...
tobias-digital Geschrieben 25. November 2004 Teilen Geschrieben 25. November 2004 Hi! Er sagt es Dir genau hier: *** GD, PNG, and/or JPEG libraries could not be located... ********* Du musst die Bibliotheken PNG und/oder JPEG zur Verfügung stellen, sprich installieren. Entweder per Hand oder über yast. Gruß Tobias Zitieren Link zu diesem Kommentar Auf anderen Seiten teilen Mehr Optionen zum Teilen...
Jessi151 Geschrieben 25. November 2004 Autor Teilen Geschrieben 25. November 2004 das hatte ich ja gemacht, ging aber nicht. hab hab mir mal die neuste gd runtergeladen und nun scheint es zu klappen... Boa, hab ich schon viel gelernt... *stolzsei* Mal sehen, denke krieg gleich wieder prob. Lag wahrscheinlich an einer alten gd Datei... Zitieren Link zu diesem Kommentar Auf anderen Seiten teilen Mehr Optionen zum Teilen...
nic_power Geschrieben 27. November 2004 Teilen Geschrieben 27. November 2004 Hallo, das hatte ich ja gemacht, ging aber nicht. Wahrscheinlich hast Du nur die Bibliotheken installiert, nicht jedoch die Development-Umgebung (Header-Files, Config-Dateien, usw.). Diese steckt meist in einem eigenen Paket mit der Endung -dev. Nic Zitieren Link zu diesem Kommentar Auf anderen Seiten teilen Mehr Optionen zum Teilen...
Empfohlene Beiträge
Dein Kommentar
Du kannst jetzt schreiben und Dich später registrieren. Wenn Du ein Konto hast, melde Dich jetzt an, um unter Deinem Benutzernamen zu schreiben.