From: bernd@petrovitsch.priv.at (Bernd Petrovitsch)
To: kernelnewbies@lists.kernelnewbies.org
Subject: gcc 2.95.3 compile failure
Date: Fri, 21 Dec 2012 10:56:57 +0100 [thread overview]
Message-ID: <1356083820.17167.45.camel@thorin> (raw)
In-Reply-To: <46e5b1e8.12b5.13bbb0380a5.Coremail.horse_rivers@126.com>
On Fre, 2012-12-21 at 09:11 +0800, horse_rivers wrote:
> At 2012-12-20 18:01:40,"Bernd Petrovitsch" <bernd@petrovitsch.priv.at> wrote:
> >On Don, 2012-12-20 at 11:11 +0800, horse_rivers wrote:
> >[....]
> >> becasue i want to compile linux 2.6 version kernel ,which require gcc2.95.3
> >
> >2.6 as such covers the range of years - look at the release dates from
> >2.6.0 and 2.6.39.
> >
> >And requirements are usually the minimum (here: oldest) version.
> >All remotely currently deployed gcc's (including from - but not limited
> >to - Debian/stable over RedHat-Enterprise-6 to SUSE/Novell with and
> >without updates) up to gcc-4.7.2 (most recent stable) should actually
> >work.
>
> that is saying the gcc4.7 can compile linux kernel 2.6.0-2.6.39 ?
Short answer: Probably - it is worth a try.
Long answer: First, I would try the gcc from your distribution - it it
works, be done with it.
Than I would try a somewhat recent one - either a prepackaged one (beu I
do not know if such actually exist somewhere) or a self-`make
bootstrap`ped one (which is IMHO easy enough).
Recent ones should understand/compile also 10 years old source ....
Bernd
--
Bernd Petrovitsch Email : bernd at petrovitsch.priv.at
LUGA : http://www.luga.at
next prev parent reply other threads:[~2012-12-21 9:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 14:10 gcc 2.95.3 compile failure horse_rivers
2012-12-19 14:35 ` Anuz Pratap Singh Tomar
2012-12-19 14:54 ` Thomas Petazzoni
2012-12-19 15:12 ` Yann Droneaud
2012-12-20 3:11 ` horse_rivers
2012-12-20 10:01 ` Bernd Petrovitsch
2012-12-21 1:11 ` horse_rivers
2012-12-21 9:17 ` sundararaj reel
2012-12-21 9:56 ` Bernd Petrovitsch [this message]
2012-12-21 10:39 ` Anuz Pratap Singh Tomar
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=1356083820.17167.45.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=kernelnewbies@lists.kernelnewbies.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).