From: Denis Vlasenko <vda@ilport.com.ua>
To: fawadlateef@gmail.com
Cc: Gireesh Kumar <gireesh.kumar@einfochips.com>,
linux-kernel@vger.kernel.org
Subject: Re: regarding kernel compilation
Date: Tue, 20 Sep 2005 11:12:27 +0300 [thread overview]
Message-ID: <200509201112.28091.vda@ilport.com.ua> (raw)
In-Reply-To: <1e62d13705092000112a49cb6c@mail.gmail.com>
On Tuesday 20 September 2005 10:11, Fawad Lateef wrote:
> On 9/20/05, Gireesh Kumar <gireesh.kumar@einfochips.com> wrote:
> > Hi,
> > I'd like to compile 2.4.20-6 kernel while running in 2.6 kernel. I tried
> > to do so but there are redeclaration errors with /kernel/sched.c and
> > /include/linux/sched.h. One it is FASTCALL and the other it is not.
> > Can anyone help me to fix this?
Kernel conpile should never use system includes, let alone
includes from _another_ kernel tree. (Using stdarg.h from gcc is ok)
> I don't think you will be able to compile 2.4 kernel on to the 2.6
> kernel based distro .... as in 2.6 based distro, mod-utils and other
2.6 modutils (module-init-tools to be exact) fall back to <toolname>.old
(by just exec'ing it) if those exist.
> packages are updated and will only support 2.6 based kernel .... So
Not true. I compiled 2.4 kernels on 2.6 machine without any problems.
> its better to get 2.4 kernel based distribution .... (and can keep/run
> both 2.6 and 2.4 based distributions simultanously on the same system,
> so that you can boot in any of them as per your requirement of 2.4 or
> 2.6 kernel)
--
vda
next prev parent reply other threads:[~2005-09-20 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-20 6:22 regarding kernel compilation Gireesh Kumar
2005-09-20 7:11 ` Fawad Lateef
2005-09-20 8:12 ` Denis Vlasenko [this message]
2005-09-20 8:37 ` Fawad Lateef
2005-09-20 8:56 ` Denis Vlasenko
2005-09-20 12:27 ` Jesper Juhl
2005-09-20 9:38 ` Mikael Pettersson
[not found] <4OJNI-Rt-1@gated-at.bofh.it>
2005-09-21 0:08 ` Robert Hancock
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=200509201112.28091.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=fawadlateef@gmail.com \
--cc=gireesh.kumar@einfochips.com \
--cc=linux-kernel@vger.kernel.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