From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: one more in cyclades
Date: Fri, 6 Dec 2002 21:26:34 -0800 [thread overview]
Message-ID: <200212070526.gB75QYY32603@work.bitmover.com> (raw)
make -f scripts/Makefile.build obj=drivers/char
gcc -Wp,-MD,drivers/char/.consolemap_deftbl.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=consolemap_deftbl -DKBUILD_MODNAME=consolemap_deftbl -c -o drivers/char/consolemap_deftbl.o drivers/char/consolemap_deftbl.c
gcc -Wp,-MD,drivers/char/.defkeymap.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=defkeymap -DKBUILD_MODNAME=defkeymap -c -o drivers/char/defkeymap.o drivers/char/defkeymap.c
gcc -Wp,-MD,drivers/char/.cyclades.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=athlon -Iarch/i386/mach-generic -fomit-frame-pointer -nostdinc -iwithprefix include -DKBUILD_BASENAME=cyclades -DKBUILD_MODNAME=cyclades -c -o drivers/char/cyclades.o drivers/char/cyclades.c
drivers/char/cyclades.c:887: parse error before `}'
make[2]: *** [drivers/char/cyclades.o] Error 1
make[1]: *** [drivers/char] Error 2
make: *** [drivers] Error 2
next reply other threads:[~2002-12-07 5:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 5:26 Larry McVoy [this message]
2002-12-09 16:01 ` [DRIVER PATCH] drivers/char/cyclades.c (it was Re: one more in cyclades) henrique
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=200212070526.gB75QYY32603@work.bitmover.com \
--to=lm@bitmover.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome