public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Mike Castle <dalgoda@ix.netcom.com>, linux-kernel@vger.kernel.org
Subject: Re: linux-2.4.28 compile problem with gcc-3.4.3
Date: Wed, 1 Dec 2004 23:46:23 +0100	[thread overview]
Message-ID: <20041201224623.GA5148@stusta.de> (raw)
In-Reply-To: <20041201221051.GR790@thune.sonic.net>

On Wed, Dec 01, 2004 at 02:10:51PM -0800, Mike Castle wrote:
> 
> Apparently, when building for a 386 kernel with gcc-3.4.3, rwsem-spinlock.c
> fails to build.
> 
> .config and typescript attached.

Thanks for this report.

This is a known bug already fixed in 2.4.29-pre1.

> mrc

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2004-12-01 22:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 22:10 linux-2.4.28 compile problem with gcc-3.4.3 Mike Castle
2004-12-01 22:46 ` Adrian Bunk [this message]
2004-12-01 23:58   ` Mike Castle
2004-12-02  0:01   ` Mike Castle

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=20041201224623.GA5148@stusta.de \
    --to=bunk@stusta.de \
    --cc=dalgoda@ix.netcom.com \
    --cc=linux-kernel@vger.kernel.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