From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, jgarzik@pobox.com,
linux-mips@linux-mips.org
Subject: Re: Compiler error in drivers/video/cirrusfb.c: syntax error before ‘volatile’
Date: Tue, 24 Jan 2006 13:58:53 +0000 [thread overview]
Message-ID: <20060124135853.GE3459@linux-mips.org> (raw)
In-Reply-To: <20060124025130.GA8418@deprecation.cyrius.com>
On Tue, Jan 24, 2006 at 02:51:30AM +0000, Martin Michlmayr wrote:
> I get the following compiler error for drivers/video/cirrusfb.c on
> mips:
>
> CC drivers/video/cirrusfb.o
> In file included from include/video/vga.h:25,
> from drivers/video/cirrusfb.c:70:
> include/asm/vga.h:29: error: syntax error before ‘volatile’
> include/asm/vga.h:34: error: syntax error before ‘volatile’
> make[2]: *** [drivers/video/cirrusfb.o] Error 1
>
> These lines define scr_writew() and scr_readw():
>
> 29:static inline void scr_writew(u16 val, volatile u16 *addr)
> 34:static inline u16 scr_readw(volatile const u16 *addr)
>
> Note that some other arches (powerpc, alpha) have the same
> definitions in vga.h.
>
> This is with 2.6.15.
Interesting catch. The reason is this code in <linux/vt_buffer.h>:
[...]
#if defined(CONFIG_VGA_CONSOLE) || defined(CONFIG_MDA_CONSOLE)
#include <asm/vga.h>
#endif
#ifndef VT_BUF_HAVE_RW
#define scr_writew(val, addr) (*(addr) = (val))
#define scr_readw(addr) (*(addr))
#define scr_memcpyw(d, s, c) memcpy(d, s, c)
[...]
But VT_BUF_HAVE_RW is defined in <asm/vga.h>, so if neither
CONFIG_VGA_CONSOLE nor CONFIG_MDA_CONSOLE is defined compilation will
blow up when <asm/vga.h> is being imported later.
Ralf
prev parent reply other threads:[~2006-01-24 13:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-24 2:51 Compiler error in drivers/video/cirrusfb.c: syntax error before ‘volatile’ Martin Michlmayr
2006-01-24 13:58 ` Ralf Baechle [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=20060124135853.GE3459@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=jgarzik@pobox.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.com \
/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.