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 19:49:05 +0530 [thread overview]
Message-ID: <8355959a0701070619w19dd79a5r5ccfdd1121e6a52b@mail.gmail.com> (raw)
In-Reply-To: <20070107132054.GA435@1wt.eu>
> > On 1/7/07, Willy Tarreau <w@1wt.eu> wrote:
> I don't see which libs you are talking about. The compiler you build your
> kernel with is totally independant on the compiler you build your apps with.
> A few years ago, some distros even shipped a compiler just for the kernel
> (they called the binary "kgcc").
>
> So you just have to build 2 different GCC, one for 2.4, one for 2.6 and
> you use them to build your kernels. If you want yet another compiler for
> your apps, simply do it, it's not a problem. For instance, look on my
> system when I type gcc- <Tab> :
Sorry for the typo & confusion caused. I meant in that example as:-
myArmWireless app. compiled with gcc-3.4.x, NOT gcc-4.1.x compiler on
say 2.4.34 kernel (assuming I can build 4.1.x on 2.4.34 kernel).
Now, I've got it about this app funda. Ok! Am coming closer now. I
have these 2 tasks:-
a) Since 2.6 kernel has no issues with gcc-3.4.x, gcc-4.1.x. So I will
build them. No probs here.
b) 2.4 kernel has no issues with gcc-3.4.x to my understanding, but am
not sure about compiling it with gcc-4.1.x? If this is true, how to
build this?
Whole idea is to have 2 compilers (gcc-3.4.x, gcc-4.1.x) on the both
the kernels.
> > Hope you guys consider these (my) questions as Novice, because am
> > trying to figure a design @ How-To build such multi kernel/gcc
> > systems.
>
> Well, I hope it will help you
> Willy
Thanks,
~Akula2
next prev parent reply other threads:[~2007-01-07 14:19 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
2007-01-07 13:20 ` Willy Tarreau
2007-01-07 14:19 ` Akula2 [this message]
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=8355959a0701070619w19dd79a5r5ccfdd1121e6a52b@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®