From: "Priit Laes" <plaes@plaes.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-handheld] Troubles building kernel for h2200
Date: Sat, 05 May 2012 23:05:54 +0300 [thread overview]
Message-ID: <1336248354.26091.4.camel@localhost.localdomain> (raw)
In-Reply-To: <4FA58128.7030906@gmail.com>
Ühel kenal päeval, L, 05.05.2012 kell 12:36, kirjutas Khem Raj:
> On 05/05/2012 09:57 AM, Priit Laes wrote:
> > include/asm/arch/uncompress.h:20:20: warning: conflicting types for
> > built-in function 'putc'
>
> what version of binutils+gcc is in play and which version of kernel is
> it ?
binutils-2.20.1-r9
gcc-4.5-r49+svnr184907
And kernel is linux-handhelds-2.6-2.6.21-hh20-r27
It's quite possible that I'm posting to the wrong place because I've set
up the system using Angstrom's setup-scripts
( https://github.com/angstrom-distribution/setup-scripts )
using the following tutorial:
http://www.angstrom-distribution.org/building-angstrom
Päikest,
Priit Laes
next prev parent reply other threads:[~2012-05-05 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-05 16:57 [meta-handheld] Troubles building kernel for h2200 Priit Laes
2012-05-05 19:36 ` Khem Raj
2012-05-05 20:05 ` Priit Laes [this message]
2012-05-05 23:32 ` Khem Raj
2012-05-06 7:14 ` Priit Laes
2012-12-22 18:36 ` Christoph Sobotka
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=1336248354.26091.4.camel@localhost.localdomain \
--to=plaes@plaes.org \
--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