From: Thomas Gleixner <tglx@linutronix.de>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Compile error in mtdblock-core...
Date: Tue, 07 Jan 2003 20:23:51 +0100 [thread overview]
Message-ID: <200301072023.51233.tglx@linutronix.de> (raw)
In-Reply-To: <3E1A97C2.DA5A0FC0@imc-berlin.de>
On Tuesday 07 January 2003 10:02, Steven Scholz wrote:
> Thomas Gleixner wrote:
> > On Monday 06 January 2003 16:19, Steven Scholz wrote:
> > > -DKBUILD_BASENAME=mtdblock_core -c -o mtdblock-core.o mtdblock-core.c
> > > In file included from
> > > /opt/BITKEEPER/Exports/linuxppc_2_4_devel-2003-01-06.test/include/linux
> > >/blk .h:4, from mtdblock-core.c:18:
> > > /opt/BITKEEPER/Exports/linuxppc_2_4_devel-2003-01-06.test/include/linux
> > >/blk dev.h:147: parse error before `struct'
> >
> > Check in blkdev.h, if the define before the struct contains any control
> > characters. Happens sometimes and gcc is not very happy with this. Should
> > not be a problem of mtd, because mtd does not modify blkdev.h.
>
> Hmm, I see. But this only happens after I used the patchin script from MTD
> CSV.
It has nothing to do with patchin. The offending line is
blkdev.h:147: extern inline int rq_data_dir(struct request *rq)
which is a backport of a 2.5 function
This is also defined in include/linux/mtd/compatmac.h, which is the
compability header for 2.4/2.5.
GCC output is not very informative, but with a little intuition and "grep" it
can be found :)
--
Thomas
________________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de
prev parent reply other threads:[~2003-01-07 18:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-06 15:19 Compile error in mtdblock-core Steven Scholz
2003-01-06 19:03 ` Thomas Gleixner
2003-01-07 9:02 ` Steven Scholz
2003-01-07 19:23 ` Thomas Gleixner [this message]
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=200301072023.51233.tglx@linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=steven.scholz@imc-berlin.de \
/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