All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Beers <bbeers@ieee.org>
To: linux-mtd@lists.infradead.org
Subject: Re:  MTD - DOC 2000 freezes on umount
Date: Tue, 20 Jan 2004 15:01:20 -0500	[thread overview]
Message-ID: <400D8910.9060102@ieee.org> (raw)
In-Reply-To: <E1Aj0eB-0006rS-Bn@pentafluge.infradead.org>


On Tue, 2004-01-20 at 13:04 -0500, Mark Richards wrote:

 >[root@localhost linux]# make xconfig
 >rm -f include/asm
 >( cd include ; ln -sf asm-i386 asm)
 >make -C scripts kconfig.tk
 >make[1]: Entering directory `/usr/src/linux-2.4.24.new.mtd/scripts'
 >cat header.tk >> ./kconfig.tk
 >./tkparse < ../arch/i386/config.in >> kconfig.tk
 >drivers/mtd/chips/Config.in: 14: unknown command
 >make[1]: *** [kconfig.tk] Error 1
 >make[1]: Leaving directory `/usr/src/linux-2.4.24.new.mtd/scripts'
 >make: *** [xconfig] Error 2 [root@localhost linux]#
 >
 >
 >Is it something I'm missing?  My kernel sources are the 2.4.24 (latest).

I saw the exact same issue.  I edited drivers/mtd/chips/Config.in by hand,
  after mtd patchin, to change the lines (14 and 59) to modify
  the 'elif' into a nested 'else if'.  After that make xconfig works.  Also as
  mentioned by dwmw2, the other make *config don't seem to have any trouble
  with those lines.  I didn't get around to it figuring out why.

-bbeers

       reply	other threads:[~2004-01-20 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Aj0eB-0006rS-Bn@pentafluge.infradead.org>
2004-01-20 20:01 ` Bob Beers [this message]
2004-01-20  2:23 MTD - DOC 2000 freezes on umount Mark Richards
2004-01-20 13:51 ` Mark Richards
2004-01-20 14:07 ` David Woodhouse
2004-01-20 15:11   ` Mark Richards
2004-01-20 18:04   ` Mark Richards
2004-01-20 18:10     ` David Woodhouse
2004-01-20 18:32       ` Mark Richards
2004-01-21  5:51       ` Mark Richards
2004-01-20 18:20     ` Matthew S. McClintock
2004-01-20 18:22       ` David Woodhouse
2004-01-20 18:28         ` Matthew S. McClintock
2004-01-23  3:35           ` Mark Richards

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=400D8910.9060102@ieee.org \
    --to=bbeers@ieee.org \
    --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 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.