From: Nagendra Singh Tomar <nagendra_tomar@adaptec.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Problems compiling kernel 2.4.18 patched with the latest patc
Date: Wed, 27 Aug 2003 17:12:03 +0000 [thread overview]
Message-ID: <marc-linux-ia64-106204691327007@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106197620015702@msgid-missing>
Bjorn,
Thanx for ur reply. I had difficulties applying the patch. I tried
it on the already patched 2.4.18 (with latest ia64 port patch as I
mentioned). I will download the 2.4.21 kernel and try patching and
compiling it. Hope that passes thru. I don't want to run a 2.6 kernel
because I have a massive kernel module that works on 2.4.18 kernel on an
IA32. To start with I would just like to see if it works on IA64 also. i
don't want to get down to porting that module to 2.6. Later, when I am
done with amking it work on 2.4.21/IA64, I will put the effort of porting
it to 2.6 series.
Is 2.4.21 also not a good choice for IA64 ?
Thanx,
tomar
On Wed, 27 Aug 2003, Bjorn Helgaas wrote:
> On Tuesday 26 August 2003 3:20 pm, Nagendra Singh Tomar wrote:
> > The kernel is 2.4.18 taken from kernel.org
> > Patch applied is linux-2.4.18-ia64-020722.diff taken from
> > http://www.kernel.org/pub/linux/kernel/ports/ia64/v2.4/
> > I get the following error
> >
> > /tmp/newhd/usr/src/linux-2.4.18-ia64/include/asm/machvec.h:82:12:
> pasting
> > "machvec_hpsim" and "." does not give a valid preprocessing token
> >
> > The detailed compilation log can be found at the end of this mail. I
> have
> > made a cross compiler tool-chain on a IA32 system, running RedHat-8.0.
> > I searched in the archives. Looks like people have faced this problem,
> but
> > it was fixed. Is it fixed for 2.4.18 or do I need a later kernel.
>
> I assume you found this message in the archives:
> http://www.gelato.unsw.edu.au/linux-ia64/0206/3530.html
>
> I don't think the 2.4.18 patch was ever updated, so you probably
> can't build a 2.4.18 generic kernel unless you want to apply the
> machvec and sba_iommu patches.
>
> That's a pretty old kernel, and the generic target was just starting
> to come together then. But I assume you have a good reason for
> wanting to use such an old kernel.
>
> Bjorn
>
next prev parent reply other threads:[~2003-08-27 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 21:32 Problems compiling kernel 2.4.18 patched with the latest patch Nagendra Singh Tomar
2003-08-27 15:54 ` Bjorn Helgaas
2003-08-27 17:12 ` Nagendra Singh Tomar [this message]
2003-08-28 15:45 ` Problems compiling kernel 2.4.18 patched with the latest patc h Bjorn Helgaas
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=marc-linux-ia64-106204691327007@msgid-missing \
--to=nagendra_tomar@adaptec.com \
--cc=linux-ia64@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