From: Auke Kok <sofar@foo-projects.org>
To: "Renato S. Yamane" <renatoyamane@mandic.com.br>
Cc: Akula2 <akula2.shark@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Multi kernel tree support on the same distro?
Date: Fri, 05 Jan 2007 08:10:09 -0800 [thread overview]
Message-ID: <459E7861.9070803@foo-projects.org> (raw)
In-Reply-To: <459E4455.8050704@mandic.com.br>
Renato S. Yamane wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Em 05-01-2007 10:04, Akula2 escreveu:
>> On 1/5/07, Auke Kok <sofar@foo-projects.org> wrote:
>>> Steve Brueggeman wrote:
>>> gcc 3.4.x works great on both 2.6 and 2.4, no issues whatsoever.
>> Do you mean I need to discard gcc 4.1.x on the distro? Or keep both?
>
> I use GCC 4.1.2 with vendor Kernel (OpenSuSE) 2.6.18.2 with no problem.
> In next weekend I will compile a new Kernel. 2.6.19.1
I was not saying that *other* compilers don't work, but merely stating that a certain
version of gcc does really well with BOTH (and most) 2.4 and 2.6 kernel sources. I doubt
that gcc-4.1.x works all that great with some of the not-so-recent 2.4 kernels.
Auke
next prev parent reply other threads:[~2007-01-05 16:10 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 [this message]
[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
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=459E7861.9070803@foo-projects.org \
--to=sofar@foo-projects.org \
--cc=akula2.shark@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=renatoyamane@mandic.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.