Tobias Exner wrote: > Dear list, > > I've got a problem while compiling the nagios-plugins on a suse 10 box. > > I already searched through the web, but I didn't any helpful information. > As I understood the compile needs the path > /usr/lib/gcc/i586-suse-linux/4.0.2/include > I don't know if that's right and how to fix it. > > The path does really not exists. >
It should have been installed along with gcc unless SuSE have broken packages. Try re-installing the gcc package and see if that works. > gcc version 4.0.2 20050901 (prerelease) (SUSE Linux) > /usr/lib/gcc/i586-suse-linux/4.0.2/cc1 -E -quiet -v - -mtune=pentium > ignoring nonexistent directory "/usr/lib/gcc/i586-suse-linux/4.0.2/include" > #include "..." search starts here: > #include <...> search starts here: > /usr/local/include > /usr/lib/gcc/i586-suse-linux/4.0.2/../../../../i586-suse-linux/include This is broken though. This path resolves to /usr/i586-suse-linux/include which I doubt should exist. I'm guessing autoconf is failing quite magnificently here for some reason. It could be because the real path is missing or because autoconf is a horrible mess. -- Andreas Ericsson andreas.erics...@op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Nagios-users mailing list Nagios-users@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
