public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: elf@buici.com
To: linux-mtd@lists.infradead.org
Subject: Building from CVS for 2.2.x
Date: Sun, 5 May 2002 09:04:27 -0700	[thread overview]
Message-ID: <20020505160427.GA9927@buici.com> (raw)
In-Reply-To: <20020505002518.GA3665@buici.com>

It appears that at least one of the include references in the CVS code
(mtd-snapshot-20020504) is not compatible with the 2.2.x kernel
series.

I'm building the kernel from a directory in my /home.  The kernel
running on the development system is 2.4.x.  I unpacked a stock 2.2.17
kernel, patched it with mtd-2.2.17.patch, and then ran patchin.sh.  I
I checked the links and found them proper and intact.

The first problem was that the spinlock types were defined twice
incompatibly.  In compactmac.h, the inclusion of linux/spinlock.h at
line 362 pulls the file from /usr/include instead of the linux source
tree version.  Changing this include to asm/spinlock.h eliminated the
problem, though I'm not confident that this is the right way to fix
it.

Then, the pci.c driver in mtd/maps failed to build, but for a reason I
couldn't deduce.  The compiler complains that the ioremap_noncache
symbol is missing.  

What might I be missing?  Is there another kernel patch?

  reply	other threads:[~2002-05-05 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020507152652.GA30979@buici.com>
     [not found] ` <20020507022357.GC17041@buici.com>
2002-05-05  0:25   ` Unclear about unwriteprotecting elf
2002-05-05 16:04     ` elf [this message]
2002-05-06 20:07     ` David Woodhouse
     [not found]       ` <25429.1020783875@redhat.com>
     [not found]         ` <27957.1020785387@redhat.com>
2002-05-07 15:50           ` Latest CVS and 2.2.x elf
2002-05-07 15:55             ` David Woodhouse

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=20020505160427.GA9927@buici.com \
    --to=elf@buici.com \
    --cc=linux-mtd@lists.infradead.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