From: Jakob Kemi <jakob.kemi@telia.com>
To: Adrian Bunk <bunk@fs.tum.de>, Rolf Fokkens <fokkensr@linux06.vertis.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] [2.4.19-rc1] w9966 doesn't compile
Date: Sat, 29 Jun 2002 14:54:09 +0200 [thread overview]
Message-ID: <200206291255.g5TCtnH25982@d1o849.telia.com> (raw)
In-Reply-To: <Pine.NEB.4.44.0206260958530.18882-100000@mimas.fachschaften.tu-muenchen.de>
On Wednesday 26 June 2002 10:20, Adrian Bunk wrote:
> On Tue, 25 Jun 2002, Rolf Fokkens wrote:
> > Hi!
>
> Hi Rolf!
Hi Rolf and Adrian!
>
> > While trying to compile 2.4.19-rc1 the following error occurs:
> >
> > w9966.c:68: warning: invalid character in macro parameter name
> > w9966.c:68: badly punctuated parameter list in `#define'
> > w9966.c:69: warning: invalid character in macro parameter name
> > w9966.c:69: badly punctuated parameter list in `#define'
> > w9966.c: In function `w9966_init':
> > w9966.c:329: warning: implicit declaration of function `DPRINTF'
> > w9966.c: In function `w9966_setup':
> > w9966.c:432: warning: implicit declaration of function `DASSERT'
> >
> > Relevant config options seem to me:
> >
> > CONFIG_VIDEO_W9966=m
>
> You are using egcs?
>
> It seems egcs can't handle the following in lines 68-69:
>
> <-- snip -->
>
> ...
> # define DPRINTF(...) do {} while(0)
> # define DASSERT(...) do {} while(0)
> ...
>
> <-- snip -->
>
>
> Since egcs is a supported compiler someone should fix this before
> 2.4.19-final comes out.
>
>
> A solution might be something like the patch below (but I don't know for
> sure whether this is the correct solution):
>
>
> --- drivers/media/video/w9966.c.old Wed Jun 26 10:08:04 2002
> +++ drivers/media/video/w9966.c Wed Jun 26 10:12:56 2002
> @@ -65,8 +65,8 @@
> DPRINTF("Assertion failed at line %d.\n", __LINE__);\
> } while (0)
> #else
> -# define DPRINTF(...) do {} while(0)
> -# define DASSERT(...) do {} while(0)
> +# define DPRINTF(x...)
> +# define DASSERT(x...)
> #endif
>
> /*
Unfortunatley I don't have egcs handy. Would this be a fix for egcs?
--- w9966.c.orig Sat Jun 29 14:23:41 2002
+++ w9966.c Sat Jun 29 14:50:21 2002
@@ -65,8 +65,8 @@
DPRINTF("Assertion failed at line %d.\n", __LINE__);\
} while (0)
#else
-# define DPRINTF(...) do {} while(0)
-# define DASSERT(...) do {} while(0)
+# define DPRINTF(f, a...) do {} while(0)
+# define DASSERT(f, a...) do {} while(0)
#endif
/*
> > Cheers,
> >
> > Rolf
>
> cu
> Adrian
Regards,
Jakob
next prev parent reply other threads:[~2002-06-29 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-25 21:54 Rolf Fokkens
2002-06-26 8:20 ` Adrian Bunk
2002-06-29 12:54 ` Jakob Kemi [this message]
2002-06-29 16:47 ` Adrian Bunk
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=200206291255.g5TCtnH25982@d1o849.telia.com \
--to=jakob.kemi@telia.com \
--cc=bunk@fs.tum.de \
--cc=fokkensr@linux06.vertis.nl \
--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
all inboxes | Powered by JetHome®