From: "andrzej zaborowski" <balrog@zabor.org>
To: Dirk Behme <dirk.behme@googlemail.com>
Cc: OMAP <Linux-omap-open-source@linux.omap.com>
Subject: Re: problem compiling kernel
Date: Mon, 27 Feb 2006 10:55:55 +0100 [thread overview]
Message-ID: <fb249edb0602270155v65302263x@mail.gmail.com> (raw)
In-Reply-To: <43F5F31B.2010503@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 543 bytes --]
On 17/02/06, Dirk Behme <dirk.behme@googlemail.com> wrote:
> [..]
> Does patch in previous mail fix this?
>
> Which toolchain do use? My toolchain doesn't complain about
> this.
My gcc 4.1.0 did complain and the patch fixed this fine. I think there
were also other errors/warning (can't remember) when compiling with
4.1.0 -- ofcourse, depending on what drivers you chose to compile in.
Sorry for late reply.
--
balrog 2oo6
Dear Outlook users: Please remove me from your address books
http://www.newsforge.com/article.pl?sid=03/08/21/143258
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2006-02-27 9:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-15 18:25 problem compiling kernel Luís Cargnini
2006-02-15 18:35 ` andrzej zaborowski
2006-02-15 19:02 ` Luís Cargnini
2006-02-17 16:00 ` Dirk Behme
2006-02-27 9:55 ` andrzej zaborowski [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=fb249edb0602270155v65302263x@mail.gmail.com \
--to=balrog@zabor.org \
--cc=Linux-omap-open-source@linux.omap.com \
--cc=balrogg@gmail.com \
--cc=dirk.behme@googlemail.com \
/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