All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails sanity check
Date: Wed, 24 Nov 2010 11:04:50 -0700	[thread overview]
Message-ID: <4CED53C2.7070109@mentor.com> (raw)
In-Reply-To: <AANLkTik7jiaQGPgnzi+AbygYSKsSTEY7jVPbk6CyRNAr@mail.gmail.com>

On 11/24/2010 10:32 AM, Zach Frey wrote:
> Hi,
>
> I'm seeing a new error using git HEAD and trying to build for the omapzoom2:
>
>
> Build Configuration:
> BB_VERSION        = "1.10.0"
> METADATA_BRANCH   = "master"
> METADATA_REVISION = "20117ec"
> TARGET_ARCH       = "arm"
> TARGET_OS         = "linux-gnueabi"
> MACHINE           = "omapzoom2"
> DISTRO            = "angstrom"
> DISTRO_VERSION    = "next"
> TARGET_FPU        = "hard"
>
> | checking how to run the C preprocessor... arm-angstrom-linux-gnueabi-gcc
> -E
> | configure: error: in
> `/home/PHOENIX/frey/OE/build/tmp/work/armv7a-angstrom-linux-gnueabi/eglibc-2.12-r16.7+svnr11982/build-arm-angstrom-linux-gnueabi':
> | configure: error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails
> sanity check
> | See `config.log' for more details.
> | ERROR: Function do_configure failed
>
> Suggestions?  More info I can provide?

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.

-- 
Tom Rini
Mentor Graphics Corporation



  reply	other threads:[~2010-11-24 18:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-24 17:32 error: C preprocessor "arm-angstrom-linux-gnueabi-gcc -E" fails sanity check Zach Frey
2010-11-24 18:04 ` Tom Rini [this message]
2010-11-24 18:23   ` Zach Frey
2010-11-24 18:40     ` Tom Rini
2010-11-24 18:56       ` Zach Frey
2010-11-24 18:42 ` Khem Raj
2010-11-24 21:19   ` Zach Frey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CED53C2.7070109@mentor.com \
    --to=tom_rini@mentor.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.