[oe] error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails sanity check

[Tom Rini]

On 11/24/2010 11:23 AM, Zach Frey wrote:
> On Wed, Nov 24, 2010 at 1:04 PM, Tom Rini<tom_rini at mentor.com>  wrote:
>
>>
>> Yes, look at the config.log file to see why it failed.  I hate to be rude
>> but it's right there in what you sent.
>
>
> No worries; I realize I am capable of staring at the obvious and not
> noticing it at times... still learning my way around the tmp/work directory
> structure.  I think I was confusing config.log and log.do_configure.
>
> So:  what is needed is
> tmp/work/armv7a-angstrom-linux-gnueabi/system-tools-backends-2.10.1-r0/system-tools-backends-2.10.1/config.log
>
> I've attached it.  This seems to be the snippet of interest?
>
> configure:6899: checking how to run the C preprocessor
> configure:6969: result: arm-angstrom-linux-gnueabi-gcc -E
> configure:6989: arm-angstrom-linux-gnueabi-gcc -E
> -isystem/home/PHOENIX/frey/OE/build/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include
> conftest.c
> configure:6989: $? = 0
> configure:7003: arm-angstrom-linux-gnueabi-gcc -E
> -isystem/home/PHOENIX/frey/OE/build/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include
> conftest.c
> conftest.c:11:28: fatal error: ac_nonexistent.h: No such file or directory
> compilation terminated.
> configure:7003: $? = 1
> configure: failed program was:
> | /* confdefs.h */
> ...

This particular config.log says at the end that it exited with status 0 
(which is the desired one..).  Perhaps a different config.log?

-- 
Tom Rini
Mentor Graphics Corporation