From: Jarek Poplawski <jarkao2@o2.pl>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: Adrian Bunk <bunk@kernel.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andi Kleen <ak@suse.de>,
linux-arch@vger.kernel.org,
Randy Dunlap <randy.dunlap@oracle.com>,
Chris Wedgwood <cw@f00f.org>,
Glauber de Oliveira Costa <glommer@gmail.com>,
linux-mips@linux-mips.org, Oliver Pinter <oliver.pntr@gmail.com>,
Greg KH <greg@kroah.com>, Al Viro <viro@ftp.linux.org.uk>,
len.brown@intel.com
Subject: Re: RFC: drop support for gcc < 4.0
Date: Wed, 22 Aug 2007 08:07:13 +0200 [thread overview]
Message-ID: <20070822060713.GA1684@ff.dom.local> (raw)
In-Reply-To: <17c0b56b663fce6f28b46e3c42dfbaf9@kernel.crashing.org>
On Wed, Aug 22, 2007 at 02:08:33AM +0200, Segher Boessenkool wrote:
> >>>How many people e.g. test -rc kernels compiled with gcc 3.2?
I confirm gcc version:
~/src/linux-2.6.23-rc3$ gcc -v
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-checkingi
--with-gnu-ld --verbose --target=i486-slackware-linux
--host=i486-slackware-linux
Thread model: posix
gcc version 3.2.3
glibc-2.3.2
Sorry, you have to guess this, but, after reporting long time ago some
acpi make warnings, I didn't even suspect anybody would be interested
more this time...
It's an old box with Slackware 9.1, and this make is the last stage
of testing such a hot kernel version... But, according to README gcc
3.2 seems to be legal. (I hope there would be some warning about gcc
too old, anyway.)
Cheers,
Jarek P.
next prev parent reply other threads:[~2007-08-22 6:08 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
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 [this message]
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=20070822060713.GA1684@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bunk@kernel.org \
--cc=cw@f00f.org \
--cc=glommer@gmail.com \
--cc=greg@kroah.com \
--cc=len.brown@intel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=oliver.pntr@gmail.com \
--cc=randy.dunlap@oracle.com \
--cc=segher@kernel.crashing.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ftp.linux.org.uk \
/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).