This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gcc 7.2.0 error: no include path in which to search for stdc-predef.h


It seems the last error preceeding the "suffix" error is "no include
path in which to search for stdc-predef.h"
"This error message is quite misleading and frequently the problem has
nothing to do with the message. You have to check the file
'config.log' in the directory where the error occurred. In the example
above, you would have to check the 'config.log' file in the directory
'/home/manu/gcc/gcc/i686-pc-linux-gnu/libgcc'. There might be several
test programs that failed during the configuration, but some of these
failures are non-critical. Check for the last error entry in the file.
I wonder where to find stdc-predef.h or whether it's generated by gcc
during compile time.
I'm also compiling against musl.

Marek

On Tue, Nov 28, 2017 at 12:19 AM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> N.B. the gcc@gcc.gnu.org mailing list is not for support. For help
> building or using GCC use the gcc-help@gcc.gnu.org mailing list (see
> https://gcc.gnu.org/lists.html for information on the lists and what's
> on-topic).
>
> On 27 November 2017 at 20:23, Jim Wilson wrote:
>> On 11/26/2017 11:09 PM, Marek wrote:
>>>
>>> Hi,
>>>
>>> while compiling 7.2.0 im getting the following:
>>>
>>> cc1: error: no include path in which to search for stdc-predef.h
>>> cc1: note: self-tests are not enabled in this build
>>
>>
>> This doesn't appear to be a build error.  Configure runs the compiler to
>> check for features, and if a check fails, then the feature is disabled. This
>> is normal, and nothing to worry about.  Though the message is unusual.  If
>> the compiler is the one you just built, there might be something wrong with
>> it.  Or there might be a minor configure script bug.
>>
>>> configure: error: in
>>> `/run/media/void/minnow/build/gcc-7.2.0/x86_64-lfs-linux-gnu/libgcc':
>>> configure: error: cannot compute suffix of object files: cannot compile
>>> See `config.log' for more details.
>>> make[1]: *** [Makefile:12068: configure-target-libgcc] Error 1
>>> make: *** [Makefile:880: all] Error 2
>>
>>
>> This is the real build error.  You need to look at the config.log file in
>> the directory where configure failed to see what the problem is. This is
>> usually a build environment problem of some sort.
>
> There's a FAQ entry about this error, please read it:
> https://gcc.gnu.org/wiki/FAQ#configure_suffix
>
>>> If gcc is able to recognize between sources in one dir and objects in
>>> another dir
>>
>>
>> Yes.  The usual way to configure gcc is something like
>>   mkdir build
>>   cd build
>>   ../gcc/configure
>
> See https://gcc.gnu.org/wiki/InstallingGCC for more information,
> including how to avoid the error above.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]