From: "Glauber de Oliveira Costa" <glommer@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Jarek Poplawski <jarkao2@o2.pl>, Adrian Bunk <bunk@kernel.org>,
Chris Wedgwood <cw@f00f.org>,
linux-arch@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: RFC: drop support for gcc < 4.0
Date: Tue, 21 Aug 2007 18:01:51 -0300 [thread overview]
Message-ID: <5d6222a80708211401g6c88753cyd239006b5ed00aea@mail.gmail.com> (raw)
In-Reply-To: <ea37408ece5ef8d2382ad551f74912eb@kernel.crashing.org>
On 8/21/07, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > Last time I tried a mips build, it would fail the compile unless I was
> > using _exactly_ 3.4.4 (I didn't tried older versions, but did try
> > 3.4.6, for ex.).
>
> If 3.4.4 works where 3.4.6 doesn't, you should report this as a
> bug; either here, or to the GCC team (but please be aware that the
> 3.4 series isn't supported anymore), or to whoever built that
> compiler for you.
I didn't bothered reporting it here because linux-mips website quotes
explicitly the dependency on 3.4.4. So at least, I imagined they are
aware of it. (And as you said, no point in reporting it to gcc...)
> > So I also think the 3.4 series will still have to be
> > around for a while.
>
> Huh? 3.4 doesn't work for you, so that's why it should stay
> a supported compiler?
3.4.4 does. anyway, by this phrase, I only meant: "Dropping support
for 3.4 series won't help in this case"
--
Glauber de Oliveira Costa.
"Free as in Freedom"
http://glommer.net
"The less confident you are, the more serious you have to act."
next prev parent reply other threads:[~2007-08-21 21:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070821132038.GA22254@ff.dom.local>
[not found] ` <20070821093103.3c097d4a.randy.dunlap@oracle.com>
2007-08-21 17:35 ` RFC: drop support for gcc < 4.0 Adrian Bunk
2007-08-21 17:54 ` Russell King
2007-08-21 18:14 ` Kyle McMartin
2007-08-21 18:29 ` Adrian Bunk
2007-08-22 5:48 ` Robert P. J. Day
2007-08-21 18:25 ` Chris Wedgwood
2007-08-21 20:41 ` Glauber de Oliveira Costa
2007-08-21 20:56 ` Segher Boessenkool
2007-08-21 21:01 ` Glauber de Oliveira Costa [this message]
2007-08-22 6:59 ` Thomas Bogendoerfer
2007-08-22 18:15 ` Ralf Baechle
2007-08-21 19:19 ` Andi Kleen
2007-08-21 19:54 ` Adrian Bunk
2007-08-21 20:07 ` [RFC][PATCH] introduce TASK_SIZE_OF() for all arches Matthew Wilcox
2007-08-21 20:08 ` RFC: drop support for gcc < 4.0 Linus Torvalds
2007-08-21 20:21 ` Adrian Bunk
2007-08-21 20:32 ` Linus Torvalds
2007-08-22 7:36 ` Jarek Poplawski
2007-08-21 20:49 ` Segher Boessenkool
2007-08-21 21:21 ` Adrian Bunk
2007-08-21 21:49 ` James Bottomley
2007-08-21 22:09 ` Adrian Bunk
2007-08-22 0:08 ` Segher Boessenkool
2007-08-22 6:07 ` Jarek Poplawski
2007-08-21 21:41 ` Oliver Pinter
2007-08-22 7:57 ` Jan Engelhardt
2007-08-22 8:08 ` Jarek Poplawski
2007-08-22 8:10 ` Jan Engelhardt
2007-08-22 8:42 ` Michal Piotrowski
2007-08-22 8:56 ` Jarek Poplawski
2007-08-22 8:48 ` Martin Michlmayr
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=5d6222a80708211401g6c88753cyd239006b5ed00aea@mail.gmail.com \
--to=glommer@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=cw@f00f.org \
--cc=jarkao2@o2.pl \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=randy.dunlap@oracle.com \
--cc=segher@kernel.crashing.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).