From: Richard How <Richard.How@einfosolutions.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: build cairo
Date: Mon, 16 Oct 2006 11:02:46 +0930 [thread overview]
Message-ID: <20061016110246.73bc9292.Richard.How@einfosolutions.com> (raw)
In-Reply-To: <20061015145613.ovhqbcfhdndc888c@webmail.neophob.com>
On Sun, 15 Oct 2006 14:56:13 +0200
michu@neophob.com wrote:
> | CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include/directfb
> | cc1: internal compiler error: in add_path, at c-incpath.c:362
> | Please submit a full bug report,
> | with preprocessed source if appropriate.
> | See <URL:http://gcc.gnu.org/bugs.html> for instructions.
I have been wrestling with this problem for a week now. Our development
board has changed from pxa255 arm processor to mipsel and I have
managed to bitbake meta-gpe and run it successfully. Now I need to bitbake
FBReader which requires enca. The configuration stage shows this in the
config.log
Extract from config.log in enca-1.9
configure:20864: checking for sqrt in -lm
configure:20894: mipsel-linux-gcc -Os -mips2 -o conftest -Wall -W -pedantic -isystem/stuff/build/tmp/staging/mipsel-linux/include -fexpensive-optimizations -fomit-frame-pointer -frename-registers -O2 -isystem/stuff/build/tmp/staging/mipsel-linux/include -I/usr/include -L/stuff/build/tmp/staging/mipsel-linux/lib -Wl,-rpath-link,/stuff/build/tmp/staging/mipsel-linux/lib -Wl,-O1 -L/usr/lib conftest.c -lm >&5
CROSS COMPILE Badness: /usr/include in INCLUDEPATH: /usr/include
cc1: internal compiler error: Aborted
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
I have found examples mentioning this problem but so far no solution.
Any help or advice would be much appreciated :)
Regards Richard
prev parent reply other threads:[~2006-10-16 1:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 12:56 build cairo michu
2006-10-15 20:36 ` Leon Woestenberg
2006-10-16 1:32 ` Richard How [this message]
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=20061016110246.73bc9292.Richard.How@einfosolutions.com \
--to=richard.how@einfosolutions.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox