From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Trying to build cmake in OE for BeagleBoard (errors)
Date: Sat, 30 May 2009 16:48:41 +0200 [thread overview]
Message-ID: <gvrh09$88g$1@ger.gmane.org> (raw)
In-Reply-To: <4A213D52.8050802@gmail.com>
On 30-05-09 16:06, Dan wrote:
> Hi all,
>
> I'm trying to build cmake in OE for the Beagle Board from Angstrom
> stable/2009. I can build
> cmake-native correctly, but that's for my host. When I try $bitbake
> cmake, I get errors. The recipe that comes in the OE repository is for
> version 2.4.8. I tried copying and pasting the .bb and renaming to the
> latest version 2.6.4 and get the same exact errors. I am able to build
> other packages like console-image correctly.
>
> Here's my errors from cmake-2.6.4:
>
>
> The cmake_bootstrap.log says this:
>
> Try: ccache
> Line: ccache -isystem/oe/tmp/staging/armv7a-angstrom-linux-gnueabi/usr/
> include -fexpensive-optimizations -frename-registers -fomit-frame-
> pointer -O2 cmake_bootstrap_31053.test.c -o cmake_bootstrap_31053.test
It seems cmake treats $CC was a single word instead of the string it is.
So instead of it doing 'ccache arm-angstrom-linux-gnueabi-gcc <stuff>'
it is doing 'ccache <stuff>'.
I think you can get around it by disabling ccache (CCACHE=""), but it
means cmake will also ignore $TARGET_CC_ARCH, which is a bit more severe.
regards,
Koen
next prev parent reply other threads:[~2009-05-30 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 14:06 Trying to build cmake in OE for BeagleBoard (errors) Dan
2009-05-30 14:48 ` Koen Kooi [this message]
2009-05-30 18:04 ` Dan
2009-05-30 18:39 ` Koen Kooi
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='gvrh09$88g$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.