SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
darkzone@darkzone:~/kismet/kismet-2007-01-R1b> ./configure
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking for a BSD-compatible install... /usr/bin/install -c
checking whether make sets $(MAKE)... yes
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
darkzone@darkzone:~/kismet/kismet-2007-01-R1b>
Quote:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by configure, which was
generated by GNU Autoconf 2.60. Invocation command line was
$ ./configure
## --------- ##
## Platform. ##
## --------- ##
hostname = darkzone
uname -m = x86_64
uname -r = 2.6.18.2-34-default
uname -s = Linux
uname -v = #1 SMP Mon Nov 27 11:46:27 UTC 2006
configure:1761: checking build system type
configure:1779: result: x86_64-unknown-linux-gnu
configure:1801: checking host system type
configure:1816: result: x86_64-unknown-linux-gnu
configure:1888: checking for gcc
configure:1904: found /usr/bin/gcc
configure:1915: result: gcc
configure:2153: checking for C compiler version
configure:2160: gcc --version >&5
gcc (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2163: $? = 0
configure:2170: gcc -v >&5
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
configure:2173: $? = 0
configure:2180: gcc -V >&5
gcc: '-V' option must have argument
configure:2183: $? = 1
configure:2206: checking for C compiler default output file name
configure:2233: gcc conftest.c >&5
configure:2236: $? = 0
configure:2282: result: a.out
configure:2287: checking whether the C compiler works
configure:2297: ./a.out
configure:2300: $? = 0
configure:2317: result: yes
configure:2324: checking whether we are cross compiling
configure:2326: result: no
configure:2329: checking for suffix of executables
configure:2336: gcc -o conftest conftest.c >&5
configure:2339: $? = 0
configure:2363: result:
configure:2369: checking for suffix of object files
configure:2395: gcc -c conftest.c >&5
configure:2398: $? = 0
configure:2421: result: o
configure:2425: checking whether we are using the GNU C compiler
configure:2454: gcc -c conftest.c >&5
configure:2460: $? = 0
configure:2467: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:2470: $? = 0
configure:2477: test -s conftest.o
configure:2480: $? = 0
configure:2494: result: yes
configure:2499: checking whether gcc accepts -g
configure:2529: gcc -c -g conftest.c >&5
configure:2535: $? = 0
configure:2542: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:2545: $? = 0
configure:2552: test -s conftest.o
configure:2555: $? = 0
configure:2685: result: yes
configure:2702: checking for gcc option to accept ISO C89
configure:2776: gcc -c -g -O2 conftest.c >&5
configure:2782: $? = 0
configure:2789: test -z "$ac_c_werror_flag" || test ! -s conftest.err
configure:2792: $? = 0
configure:2799: test -s conftest.o
configure:2802: $? = 0
configure:2822: result: none needed
configure:2898: checking for g++
configure:2914: found /usr/bin/g++
configure:2925: result: g++
configure:2956: checking for C++ compiler version
configure:2963: g++ --version >&5
g++ (GCC) 4.1.2 20061115 (prerelease) (SUSE Linux)
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2966: $? = 0
configure:2973: g++ -v >&5
Using built-in specs.
Target: x86_64-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++,objc,fortran,obj-c++,java,ada --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib64 --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=x86_64-suse-linux
Thread model: posix
gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)
configure:2976: $? = 0
configure:2983: g++ -V >&5
g++: '-V' option must have argument
configure:2986: $? = 1
configure:2989: checking whether we are using the GNU C++ compiler
configure:3018: g++ -c conftest.cpp >&5
configure:3024: $? = 0
configure:3031: test -z "$ac_cxx_werror_flag" || test ! -s conftest.err
configure:3034: $? = 0
configure:3041: test -s conftest.o
configure:3044: $? = 0
configure:3058: result: yes
configure:3063: checking whether g++ accepts -g
configure:3093: g++ -c -g conftest.cpp >&5
configure:3099: $? = 0
configure:3106: test -z "$ac_cxx_werror_flag" || test ! -s conftest.err
configure:3109: $? = 0
configure:3116: test -s conftest.o
configure:3119: $? = 0
configure:3249: result: yes
configure:3285: checking for a BSD-compatible install
configure:3341: result: /usr/bin/install -c
configure:3352: checking whether make sets $(MAKE)
configure:3373: result: yes
configure:3387: checking how to run the C preprocessor
configure:3427: gcc -E conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3427: gcc -E conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3427: gcc -E -traditional-cpp conftest.c
In file included from /usr/include/features.h:324,
from /usr/include/assert.h:37,
from conftest.c:12:
/usr/include/sys/cdefs.h:32: error: #error "You need a ISO C conforming compiler to use the glibc headers"
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3427: gcc -E -traditional-cpp conftest.c
In file included from /usr/include/features.h:324,
from /usr/include/assert.h:37,
from conftest.c:12:
/usr/include/sys/cdefs.h:32: error: #error "You need a ISO C conforming compiler to use the glibc headers"
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3427: /lib/cpp conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3427: /lib/cpp conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3433: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3517: result: /lib/cpp
configure:3546: /lib/cpp conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3552: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3546: /lib/cpp conftest.c
In file included from /usr/include/bits/posix1_lim.h:153,
from /usr/include/limits.h:145,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:122,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/syslimits.h:7,
from /usr/lib64/gcc/x86_64-suse-linux/4.1.2/include/limits.h:11,
from conftest.c:9:
/usr/include/bits/local_lim.h:36:26: error: linux/limits.h: No such file or directory
configure:3552: $? = 1
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| /* end confdefs.h. */
| #ifdef __STDC__
| # include <limits.h>
| #else
| # include <assert.h>
| #endif
| Syntax error
configure:3628: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.
It looks like your machine’s include header files are all messed up (can’t find linux/limits.h). Try (re)installing whatever packages are packages are necessary for your distro (e.g., kernel-headers, system-headers, libc-headers, or something like that).
My question had little to do with your choice of distro. All I asked was whether (on your current machine and setup) you had tried to compile any other software from scratch (i.e., ./configure && make), and whether you had similar problems. If you previously had no problems, but now you do, is there anything different that you have done to the packages installed on you system (e.g., in an attempt to purge useless packages from you may have accidentally removed the system include files).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.