From: John Covici <covici@ccs.covici.com>
To: linux-kernel@vger.kernel.org
Subject: bio.h problem in kernel 2.5.21
Date: Wed, 12 Jun 2002 05:33:53 -0400 [thread overview]
Message-ID: <m3fzzssuwu.fsf@ccs.covici.com> (raw)
vmalloc.c seems to have a problem with bio.h -- at least all the
errors are in there in 2.5.21.
Any assistance would be appreciated.
gcc -Wp,-MD,.vmalloc.o.d -D__KERNEL__ -I/usr/src/linux-2.5.21/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -malign-functions=4 -nostdinc -iwithprefix include -DKBUILD_BASENAME=vmalloc -c -o vmalloc.o vmalloc.c
In file included from /usr/src/linux-2.5.21/include/linux/highmem.h:5,
from vmalloc.c:13:
/usr/src/linux-2.5.21/include/linux/bio.h:90: parse error before `atomic_t'
/usr/src/linux-2.5.21/include/linux/bio.h:90: warning: no semicolon at end of struct or union
/usr/src/linux-2.5.21/include/linux/bio.h:95: parse error before `}'
make[2]: *** [vmalloc.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.5.21/mm'
make[1]: *** [mm] Error 2
make[1]: Leaving directory `/usr/src/linux-2.5.21'
make: *** [make_with_config] Error 2
--
John Covici
covici@ccs.covici.com
reply other threads:[~2002-06-12 9:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=m3fzzssuwu.fsf@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=linux-kernel@vger.kernel.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.