From: Akula2 <akula2.shark@gmail.com>
To: "Willy Tarreau" <w@1wt.eu>
Cc: "Steve Brueggeman" <xioborg@mchsi.com>,
"Auke Kok" <sofar@foo-projects.org>,
linux-kernel@vger.kernel.org
Subject: Re: Multi kernel tree support on the same distro?
Date: Sun, 7 Jan 2007 18:41:00 +0530 [thread overview]
Message-ID: <8355959a0701070511v55c671dibc3bb7d4426129e0@mail.gmail.com> (raw)
In-Reply-To: <20070107093057.GS24090@1wt.eu>
On 1/7/07, Willy Tarreau <w@1wt.eu> 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.
That's correct about gcc-3.4.x & gcc-4.1.x about 2.6 tree support.
This means 2.6 supports both gcc versions. Here are the binaries I do
use:-
http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/Fedora/RPMS/gcc-3.4.2-6.fc3.i386.rpm
http://download.fedora.redhat.com/pub/fedora/linux/core/3/i386/os/Fedora/RPMS/kernel-2.6.9-1.667.i686.rpm
Now issue remains with 2.4 tree. Is it possible to build/install
gcc-4.1.x along with gcc-3.4.x? This is what am trying to figure by
few tests on the FC3 base machine.
Can we call this as backward compatibility?
Any inputs here is helpful :-)
> 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.
I did understand this, thanks. I have one doubt: Imagine I have
built/installed these:-
2.4.34 & 2.6.20 kernels has these gcc-3.4.x & gcc-4.1.x compilers
built on say FC6 box. Now issue comes when I run an application. How
does it understand which library use?
example:
myArmWireless app. needs gcc-3.4.x, NOT gcc-2.6.x libs on say 2.4.34 kernel.
Will it take automatically? Or we need to pass args to target the
gcc-3.4.x libs?
Hope you guys consider these (my) questions as Novice, because am
trying to figure a design @ How-To build such multi kernel/gcc
systems.
> Regards,
> Willy
~Akula2
next prev parent reply other threads:[~2007-01-07 13:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-04 19:46 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
2007-01-07 13:11 ` Akula2 [this message]
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=8355959a0701070511v55c671dibc3bb7d4426129e0@mail.gmail.com \
--to=akula2.shark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sofar@foo-projects.org \
--cc=w@1wt.eu \
--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
all inboxes | Powered by JetHome®