All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mirco Fuchs <mircofuchs@web.de>
To: linux-mtd@lists.infradead.org
Subject: 2.6.16 compile error with latest cvs mtd source
Date: Fri, 24 Mar 2006 08:16:39 +0100	[thread overview]
Message-ID: <459451265@web.de> (raw)

Thanks for your fast reply.

>> Hello,
>>>
>> i have a problem compiling the 2.6.16 kernel for my csb637 board. I think this
>> is an mtd related question because it works without patching the kernel
>> against the mtd source code.
>>
>> I have gcc 3.4.4 and binutils 2.16 and glibx 2.3.5.
>>
>> The first step was compiling the 2.6.16 kernel without patching against the
>> mtd cvs sources. --> The compilation was successfull.
>>
>> But patching the kernel against the head of the mtd cvs repo resulted in the
>> following warnings and errors:
>>
>> (I used the command 'patchkernel.sh -2cyv $KERNELDIR' for patching)

>Did you enable CONFIG_OBSOLETE_INTERMODULE in your .config? That was
>added in the 2.6.16 kernel because the inter_module stuff should
>really go away sometime.

>Alternatively, the MTD subsystem should also probably select that
>Kconfig option so users don't see this. But MTD needs a sync anyway.

I do not find CONFIG_OBSOLETE_INTERMODULE in my .config file, is there a
patch concering this?

Mirco
______________________________________________________________
Verschicken Sie romantische, coole und witzige Bilder per SMS!
Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193

             reply	other threads:[~2006-03-24  7:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24  7:16 Mirco Fuchs [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-03-23 12:02 2.6.16 compile error with latest cvs mtd source Mirco Fuchs
2006-03-23 13:10 ` Josh Boyer

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=459451265@web.de \
    --to=mircofuchs@web.de \
    --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.