From: tglx@linutronix.de (Thomas Gleixner)
To: Kalev Lember <kalev@colleduc.ee>, linux-mtd@lists.infradead.org
Subject: Re: CVS compile errors
Date: Sun, 4 Apr 2004 14:21:11 +0200 [thread overview]
Message-ID: <200404041421.11425.tglx@linutronix.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0404041514100.12090-100000@kiire.colleduc.ee>
On Sunday 04 April 2004 14:21, Kalev Lember wrote:
> Hi,
>
> I just wanted to notify that current CVS code as of 04/04/04 does not
> compile. Last snapshot that does compile is mtd-snapshot-20040327.
>
> You probably know that, but I am reporting anyhow.
>
> I have set the following options:
> CONFIG_MTD=y
> CONFIG_INFTL=y
> CONFIG_MTD_DOC2001PLUS=y
> CONFIG_MTD_DOCPROBE=y
> CONFIG_MTD_DOCPROBE_ADDRESS=0
> CONFIG_MTD_NAND=y
> CONFIG_MTD_NAND_IDS=y
>
> Linux kernel version is 2.6.4.
> Output from make is:
>
> make -f scripts/Makefile.build obj=drivers/mtd/devices
> gcc -Wp,-MD,drivers/mtd/devices/.doc2001plus.o.d -nostdinc -iwithprefix
> include -D__KERNEL__ -Iinclude -D__KERNEL__ -Iin
> clude -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
> -fno-common -pipe -mpreferred-stack-boundary=2 -march
> =pentium-mmx -Iinclude/asm-i386/mach-default -O2 -fomit-frame-pointer
> -Wdeclaration-after-statement -DKBUILD_BASENAME=do
> c2001plus -DKBUILD_MODNAME=doc2001plus -c -o
> drivers/mtd/devices/doc2001plus.o drivers/mtd/devices/doc2001plus.c
> drivers/mtd/devices/doc2001plus.c: In function `DoC_IdentChip':
> drivers/mtd/devices/doc2001plus.c:339: error: structure has no member
> named `chipshift'
> make[3]: *** [drivers/mtd/devices/doc2001plus.o] Error 1
> make[2]: *** [drivers/mtd/devices] Error 2
> make[1]: *** [drivers/mtd] Error 2
> make: *** [drivers] Error 2
>
> And indeed, there is no member named chipshift in nand.h.
I'm in the middle of an overhaul of nand stuff. I modified the id structure
and forgot to adjust the doc stuff. I have a look into it
--
Thomas
________________________________________________________________________
"Free software" is a matter of liberty, not price. To understand the concept,
you should think of "free" as in "free speech,'' not as in "free beer".
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
next prev parent reply other threads:[~2004-04-04 12:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 12:21 CVS compile errors Kalev Lember
2004-04-04 12:21 ` Thomas Gleixner [this message]
2004-04-04 12:34 ` Thomas Gleixner
2004-04-04 15:03 ` Kalev Lember
2004-04-07 1:13 ` Jon Schlueter
2004-04-07 5:47 ` andreas.huebner
2004-04-07 8:14 ` Thomas Gleixner
2004-04-07 8:15 ` Thomas Gleixner
2004-04-07 8:27 ` Thomas Gleixner
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=200404041421.11425.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=kalev@colleduc.ee \
--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