From: Willy Tarreau <w@1wt.eu>
To: Steve Brueggeman <xioborg@mchsi.com>
Cc: Auke Kok <sofar@foo-projects.org>,
Akula2 <akula2.shark@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Multi kernel tree support on the same distro?
Date: Sun, 7 Jan 2007 10:30:57 +0100 [thread overview]
Message-ID: <20070107093057.GS24090@1wt.eu> (raw)
In-Reply-To: <tekrp2tqo78uh6g2pjmrhe0vpup8aalpmg@4ax.com>
On Thu, Jan 04, 2007 at 10:28:12PM -0600, Steve Brueggeman wrote:
> There are some difficulties with gcc versions between linux-2.4 and linux-2.6,
> but I do not recall all of the details off of the top of my head. If I recall
> correctly, one of the issues is, linux-2.4 ?prefers? gcc-2.96, while newer
> linux-2.6 support/prefer gcc-3.? or greater.
2.4 was designed for gcc 2.95.3 and supports gcc up to 3.4 on all platforms,
and up to 4.1 on x86, x86_64, ppc and sparc64. Recent gcc 3.4 produces good
code on 2.4, and is able to efficiently optimize for size (-Os) without too
much speed compromise.
> At any rate, what I've done is create a chroot environment. I created this
> chroot directory by installing an older distribution that was created with
> linux-2.4 in mind (example, RedHat v8.2) into that at chroot directory. The
> easiest way to do this that I'm aware of is to install the older distribution
> (minimal development, no server junk, no X junk) on another computer, then copy
> from that computer to a directory on your development computer.
Hmm, I think you did it the *hard* way. Gcc has been supporting
multi-version for years. You just have to compile it with --suffix=-3.4
or --suffix=4.1 to have a whole collection of gcc versions on your host.
If you don't want to recompile gcc, simply rename the binaries and you're
OK. When you build, you only have to do :
$ make bzImage modules CC=gcc-3.4
I've been using it like this for years without problem. It's really
convenient, and it also allows you to easily compare output codes and
sizes between compilers.
Regards,
Willy
next prev parent reply other threads:[~2007-01-07 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 19:46 Multi kernel tree support on the same distro? Akula2
2007-01-04 20:23 ` Kristof Provost
2007-01-05 11:50 ` Akula2
2007-01-05 0:14 ` Auke Kok
2007-01-05 4:28 ` Steve Brueggeman
2007-01-05 7:30 ` Auke Kok
2007-01-05 12:04 ` Akula2
2007-01-05 12:28 ` Renato S. Yamane
2007-01-05 16:10 ` Auke Kok
[not found] ` <8355959a0701050402g673f446em1c263dea826f3bcb@mail.gmail.com>
[not found] ` <459E77D9.8080209@foo-projects.org>
2007-01-07 9:13 ` Akula2
2007-01-07 9:30 ` Willy Tarreau [this message]
2007-01-07 13:11 ` Akula2
2007-01-07 13:20 ` Willy Tarreau
2007-01-07 14:19 ` Akula2
2007-01-07 14:32 ` Willy Tarreau
2007-01-07 17:52 ` Akula2
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=20070107093057.GS24090@1wt.eu \
--to=w@1wt.eu \
--cc=akula2.shark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sofar@foo-projects.org \
--cc=xioborg@mchsi.com \
/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