All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <typedef@eircom.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] GCC version for Linux kernel?
Date: Wed, 15 Jun 2005 09:56:22 +0100	[thread overview]
Message-ID: <42AFED36.8040604@eircom.net> (raw)
In-Reply-To: <200506151046.19136.g.jaeger@sysgo.com>

Gerhard Jaeger wrote:
> On Wednesday 15 June 2005 09:12, Marc Leeman wrote:
> 
>>>Warning!  from gcc-3.3 to gcc-3.4 the handling of the attribute
>>>'unused' changed.  For that reason, compiling a linux-2.4 kernel
>>>with gcc-3.4 will break silently!
>>
>>Euhm. I've been doing this for 5 months without any problem for PPC.
>>
> 
> 
> Same here ;)
> 
> Compiling U-Boot (latest CVS) is no problem on gcc-3.4.3, as long, as
> you are not addressing ARM targets and of course it works!
> 
> For kernel compilation, you need at least kernel 2.4.28 or higher when
> using gcc 3.4.x - or some patches that fix these attribute issues
> (and other stuff, that changed)


Ah yes, someone (you?) already mentioned that on linuxppc-embedded.

I run 2.4.28-pre3 !

  reply	other threads:[~2005-06-15  8:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-13 22:19 [U-Boot-Users] GCC version for Linux kernel? Allen Curtis
2005-06-14  3:53 ` Wolfgang Denk
2005-06-14  7:14   ` Marc Leeman
2005-06-14  9:27     ` Bryan O'Donoghue
2005-06-14 10:48       ` Marc Leeman
2005-06-14 14:19         ` Allen Curtis
2005-06-14 14:59           ` Marc Leeman
2005-06-14 18:11           ` Detlef Vollmann
2005-06-15  7:12             ` Marc Leeman
2005-06-15  8:45               ` Bryan O'Donoghue
2005-06-15  8:46               ` Gerhard Jaeger
2005-06-15  8:56                 ` Bryan O'Donoghue [this message]
2005-06-15 17:12                 ` Allen Curtis
2005-06-15  9:58               ` Detlef Vollmann
2005-06-14 14:58     ` Allen Curtis

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=42AFED36.8040604@eircom.net \
    --to=typedef@eircom.net \
    --cc=u-boot@lists.denx.de \
    /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.