From: Marek Habersack <grendel@caudium.net>
To: Stefan Kleyer <kleyer@foni.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19rc3-ac4 parse error
Date: Mon, 29 Jul 2002 22:39:10 +0200 [thread overview]
Message-ID: <20020729203910.GA1722@thanes.org> (raw)
In-Reply-To: <20020729221759.1576dd0d.kleyer@foni.net>
[-- Attachment #1: Type: text/plain, Size: 617 bytes --]
On Mon, Jul 29, 2002 at 10:17:59PM +0200, Stefan Kleyer scribbled:
> Hi,
>
> I get this error while compiling:
My guess is that you're using gcc 2.95 possibly from Debian? (Other distros
might be affected too, I don't know). The cpp shipped with the Debian's gcc
2.95-15 doesn't parse the ##arg part of the varargs macro DRM_ERROR (or any
other) for that matter. It is supposed, per docs, to remove the comma should
the variable args (the "rest") be empty - it leaves the comma there instead,
which renders incorrect C code. I have submitted the bug to the Debian
gcc maintainers.
greetings,
marek
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-07-29 20:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 20:17 2.4.19rc3-ac4 parse error Stefan Kleyer
2002-07-29 20:39 ` Marek Habersack [this message]
2002-07-29 21:12 ` Stefan Kleyer
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=20020729203910.GA1722@thanes.org \
--to=grendel@caudium.net \
--cc=kleyer@foni.net \
--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