public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Juan Ramon Jimenez Garcia <juan@hispafuentes.com>
To: linux-mtd@lists.infradead.org, olea@hispafuentes.com
Subject: Problems compiling kernel 2.2.17
Date: Wed, 01 Aug 2001 13:08:38 +0200	[thread overview]
Message-ID: <3B67E336.B7925626@hispafuentes.com> (raw)

          Hi all

              We are trying to compile kernel 2.2.17 with the mtd patch,
and we have some problems.  While make bzdisk or bzImage we get a link
error:

            drivers/mtd/mtdlink.o: In function `init_mtd':
            drivers/mtd/mtdlink.o(.text.init+0x3c): undefined reference
to   `init_mtd_devices'

That have been solved modifying  GNUmakefile  like someone (Jan Rovins)
told here
           ifeq ($(VERSION),2)
              ifeq ($(PATCHLEVEL),0) <<<changed this to:>>>  ifeq
($(PATCHLEVEL),2)
                     obj-y += initcalls.o
              endif
          endif

but now we got another link error with an undefined reference to
'init_nftl'
How can we solved this?
Do you think we must to configure something special to get the kernel
image?

Thanks for your time!
J

                                ///
                               (@ @)
 ------------------------oOO----(_)----OOo-------------------------

 - Mejor no hacer nada que hacer cualquier cosa. - Francis Picabia -

 ------------------------------------------------------------------

 ¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸

    Juan Ramon Jimenez Garcia
    Hispafuentes
    Tfno 91 4575330
    juan@hispafuentes.com

 ¤º°°º¤ø,¸¸,ø¤º°°º¤ø,¸¸,ø¤º°`°º¤ø,¸

             reply	other threads:[~2001-08-01 11:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-01 11:08 Juan Ramon Jimenez Garcia [this message]
2001-08-01 11:33 ` Problems compiling kernel 2.2.17 Vipin Malik
2001-08-01 11:54   ` olea
2001-08-01 17:35     ` olea
2001-08-07  9:42   ` David Woodhouse
2001-08-07  9:48 ` David Woodhouse
2001-08-07 11:34   ` Problems compiling kernel 2.2.1-rmk2 Alex Liao
2001-08-07 12:16     ` 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=3B67E336.B7925626@hispafuentes.com \
    --to=juan@hispafuentes.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=olea@hispafuentes.com \
    /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