From: Marko Kreen <marko@l-t.ee>
To: Matti Aarnio <matti.aarnio@zmailer.org>
Cc: Thorsten Glaser Geuer <eccesys@topmail.de>, linux-kernel@vger.kernel.org
Subject: Re: Still cannot compile, 2.4.3-ac6
Date: Sun, 15 Apr 2001 00:56:24 +0200 [thread overview]
Message-ID: <20010415005624.A11455@l-t.ee> (raw)
In-Reply-To: <20010414210834.4D195A5A843@www.topmail.de> <20010415010335.X805@mea-ext.zmailer.org>
In-Reply-To: <20010415010335.X805@mea-ext.zmailer.org>; from matti.aarnio@zmailer.org on Sun, Apr 15, 2001 at 01:03:35AM +0300
On Sun, Apr 15, 2001 at 01:03:35AM +0300, Matti Aarnio wrote:
> On Sat, Apr 14, 2001 at 09:09:00PM +0000, Thorsten Glaser Geuer wrote:
> > Dear Sirs,
> > I still cannot compile with gcc-3.0 from 08.04.
>
> Yes ? Who said gcc-3.0 is suitable compiler ?
>
> No doubt it some day will be the default compiler, but not yet.
Sorry. Who said it should not be tested? How else it could get
'default compiler'? If the gcc-3.0 would start giving errors
on some old code then it could be gcc bug. But this rwsem code
is couple of days old. It is good to let it through stricter
error checking, I guess. This rwsem is very in-flux code. eg.
2.4.4-pre2 did not compile. ac[56] with um-arch do not compile.
If nothing else convinces, then AFAIK both Linus and Alan
expressed interest in seeing reports of using newer gcc's.
Remember, gcc-3.0 is in freeze since Feb 12. (Ofcourse they
also suggested against using random CVS snapshot as default
compiler in distrubution).
--
marko
next prev parent reply other threads:[~2001-04-14 22:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-14 21:09 Still cannot compile, 2.4.3-ac6 Thorsten Glaser Geuer
2001-04-14 22:03 ` Matti Aarnio
2001-04-14 22:56 ` Marko Kreen [this message]
2001-04-15 0:02 ` John Jasen
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=20010415005624.A11455@l-t.ee \
--to=marko@l-t.ee \
--cc=eccesys@topmail.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.aarnio@zmailer.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 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.