GCC build problem (#include_next limits.h)
Solution 1
I have encountered this problem doing a cross-compile. When you execute a 'make depend' the Makefile will invoke the makedepend program as seen from this assignment:
MAKEDEPPROG=makedepend
makedepend only searches some default include directories starting with /usr/include
Since the #include_next
directive means to include the next found instance of the named include file in the search path, this will fail if another one is not found.
For me, the solution was to direct makedepend to search my cross-compiler include directories first. I did this by changing the MAKEDEPPROG
assignment to include the -I
directive:
MAKEDEPPROG=makedepend -I < path/to/cross-compiler/include-fixed >
I suggest reading about the makedepend program (about which I knew nothing before). For example, it was not obvious to me that makedepend would not use an environment search path. The -I
directive puts the specified search path before makedepend's default paths.
Solution 2
I had faced my problem with compiling with STLport 5.1.5, but looks like the issue is fixed is STLport 5.2.0. The issue is documented in STLport Release Notes. After getting a copy of STLport 5.2.1, the compilation went successfully without hiccups.
Solution 3
This is most likely this issue: https://jira.apache.org/jira/browse/STDCXX-768. The workaround for me was to add the compiler option -I/usr/lib/gcc/x86_64-linux-gnu/4.3/include-fixed (this path contains limits.h).
Mars
Python haxxorz and parapsychology student. Creator of the eminent finplot library: https://github.com/highfestiva/finplot. Once upon a time made a UFO short documentary in Swedish: https://www.youtube.com/watch?v=HFF528pc3O8. Constantly at a fork in the road.
Updated on July 09, 2022Comments
-
Mars almost 2 years
When i try to
$ make depend -f gcc.mak
a middleware on my Ubuntu machine I get this
/usr/include/../include/limits.h:125:26: error: no include path in which to search for limits.h
This is the contents around limits.h:125:
/* Get the compiler's limits.h, which defines almost all the ISO constants. We put this #include_next outside the double inclusion check because it should be possible to include this file more than once and still get the definitions from gcc's header. */ #if defined __GNUC__ && !defined _GCC_LIMITS_H_ /* `_GCC_LIMITS_H_' is what GCC's file defines. */ # include_next <limits.h> #endif
I tried setting
$ export INCLUDE=/usr/lib/gcc/x86_64-linux-gnu/4.3/include-fixed/ $ export C_INCLUDE_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.3/include-fixed/ $ export CPLUS_INCLUDE_PATH=/usr/lib/gcc/x86_64-linux-gnu/4.3/include-fixed/
(which is where I found another limits.h on my system). I already have libc6-dev installed, could it be that its limits.h has been overwritten by another package? Do I need another -dev package? Or is an environment variable required; perhaps this could be circumvented in some other way?
-
Mars about 15 yearsI don't have any other (sensible) limits.h. I need the GCC limits.h. The one in include-fixed seems... off.
-
Rafael Lima about 6 yearsit was better to not say nothing
-
Rafael Lima about 6 yearswhere should i put it?
-
Mars about 6 years@RafaelLima: possibly for some; for me it would have been more useful to find out that I was lacking packages (than thinking there was something misconfigured in my system).