From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "embedded.yogesh" <embedded.yogesh@gmail.com>
Cc: poky@yoctoproject.org
Subject: Re: chromium browser
Date: Tue, 22 Feb 2011 11:13:09 +0000 [thread overview]
Message-ID: <1298373189.11289.3266.camel@rex> (raw)
In-Reply-To: <4D61F90D.606@gmail.com>
Hi,
On Mon, 2011-02-21 at 11:03 +0530, embedded.yogesh wrote:
> I tried to pull Chrome from OpenEmbedded and also pulled in its deps .
> But at the time of building chrome getting following errors can any one
> have any idea ?
>
> | + oe_runmake -r BUILDTYPE=Release
> | + '[' xmake = x ']'
> | + oenote make -e MAKEFLAGS= -r BUILDTYPE=Release
> | elease'
> | NOTE: make -e MAKEFLAGS= -r BUILDTYPE=Release
> | + make -e MAKEFLAGS= -r BUILDTYPE=Release
> | CXX(target) out/Release/obj.target/app_base/ui/base/animation/animation.o
> | cc1plus: warnings being treated as errors
> | cc1plus: error: include location "/usr/include/libpng12" is unsafe for cross-compilation
> | cc1plus: error: include location "/usr/include/gtk-2.0" is unsafe for cross-compilation
> | cc1plus: error: include location "/usr/include/atk-1.0" is unsafe for cross-compilation
> | cc1plus: error: include location
Its accessing parts of the build system (/usr/include) and the compiler
is turning warnings into errors and failing. You need to fix the build
to use the sysroot for cross compiling and not to look at the build
system.
Cheers,
Richard
next prev parent reply other threads:[~2011-02-22 11:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-07 4:52 chromium browser yogesh lal
2011-02-07 12:15 ` Gary Thomas
2011-02-07 12:51 ` embedded.yogesh
2011-02-07 18:23 ` Darren Hart
2011-02-07 18:35 ` Gary Thomas
2011-02-08 4:02 ` embedded.yogesh
2011-02-21 5:33 ` embedded.yogesh
2011-02-22 11:13 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-07 8:30 Praveenreddy Padamati
2016-03-07 9:11 ` Gary Thomas
2016-03-07 10:57 ` Praveenreddy Padamati
2016-03-07 11:05 ` Khem Raj
2016-03-07 11:43 ` Gary Thomas
2016-03-08 7:03 ` Praveenreddy Padamati
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=1298373189.11289.3266.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=embedded.yogesh@gmail.com \
--cc=poky@yoctoproject.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.