public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Manuel McLure <manuel@mclure.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.3-ac12
Date: Sun, 22 Apr 2001 13:18:03 +0100	[thread overview]
Message-ID: <20010422131803.C20807@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20010421211722.C976@ulthar.internal.mclure.org> <E14rIiE-0005h2-00@the-village.bc.nu>
In-Reply-To: <E14rIiE-0005h2-00@the-village.bc.nu>; from alan@lxorguk.ukuu.org.uk on Sun, Apr 22, 2001 at 01:11:31PM +0100

On Sun, Apr 22, 2001 at 01:11:31PM +0100, Alan Cox wrote:
> This is from Linus tree. You currently need gcc 2.96 or higher to build
> the 2.4.x kernel. 

Which goes back to the old argument that 2.96 is a redhat-ism and not a
real compiler.

To date, no 2.96 version of gcc works properly on ARM, and I for one don't
have the expertise necessary to fix gcc myself.  Do you recommend that I
stop all ARM work because of this? ;(

Anyway, the work around is a trivial one that I've already posted to the
list, including the necessary GCC version tests.  Additionally David
Howells has posted a patch to remove the __builtin_expect stuff, so
this is a non-issue now.

--
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2001-04-22 12:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-22  2:53 Linux 2.4.3-ac12 Alan Cox
2001-04-22  4:17 ` Manuel McLure
2001-04-22  5:47   ` junio
2001-04-22  6:07   ` junio
2001-04-22 10:42     ` Philip Blundell
2001-04-22 12:26       ` Alan Cox
2001-04-22 12:43         ` Philip Blundell
2001-04-22 12:54           ` Alan Cox
2001-04-22 13:00             ` Philip Blundell
2001-04-22 13:10               ` Alan Cox
2001-04-22 13:22                 ` Russell King
2001-04-22 13:29                   ` Alan Cox
2001-04-22 16:12                     ` Jes Sorensen
2001-04-22 16:30                       ` Mohammad A. Haque
2001-04-22 17:27                       ` Roman Zippel
2001-04-22 17:43                         ` Jes Sorensen
2001-04-22 18:42                       ` Alan Cox
2001-04-23  6:54                       ` Geert Uytterhoeven
2001-04-22 13:51                 ` Philip Blundell
2001-04-22 12:11   ` Alan Cox
2001-04-22 12:18     ` Russell King [this message]
2001-04-22 12:51       ` Alan Cox
2001-04-22 12:55     ` John Jasen
2001-04-22 13:00       ` Alan Cox
2001-04-22  8:57 ` Eyal Lebedinsky
2001-04-22 12:20   ` Alan Cox
2001-04-22 13:04     ` Eyal Lebedinsky
2001-04-22 16:25 ` John Cavan
2001-04-22 17:07   ` Manuel McLure
2001-04-22 18:48     ` Alan Cox
2001-04-22 18:57       ` Manuel McLure
2001-04-22 18:59       ` Linux 2.4.3-ac12 unresolved symbol rwsem J Sloan
2001-04-23  0:19       ` Linux 2.4.3-ac12 John Cavan
2001-04-23  8:35       ` Byeong-ryeol Kim
2001-04-23 22:18         ` Byeong-ryeol Kim
2001-04-22 22:46 ` Mr. James W. Laferriere
  -- strict thread matches above, loose matches on Subject: below --
2001-04-22 13:48 f5ibh
2001-04-22 14:03 ` Jesper Juhl
2001-04-22 17:26 Dieter Nützel
2001-04-22 19:53 ` J . A . Magallon

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=20010422131803.C20807@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manuel@mclure.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