From: grendel@thanes.org (Grendel)
To: Erik Andersen <andersen@codepoet.org>, Alan Cox <alan@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.19-rc3-ac4
Date: Mon, 29 Jul 2002 22:51:47 +0200 [thread overview]
Message-ID: <20020729205147.GB1722@thanes.org> (raw)
In-Reply-To: <20020729204424.GA4449@codepoet.org>
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
On Mon, Jul 29, 2002 at 02:44:25PM -0600, Erik Andersen scribbled:
[snip]
> drm_stub.h:125: parse error before `)'
> drm_stub.h:133: parse error before `)'
> drm_stub.h:137: parse error before `)'
> make[3]: *** [radeon_drv.o] Error 1
> make[3]: Leaving directory `/usr/src/linux/drivers/char/drm'
> make[2]: *** [_modsubdir_drm] Error 2
> make[2]: Leaving directory `/usr/src/linux/drivers/char'
> make[1]: *** [_modsubdir_char] Error 2
> make[1]: Leaving directory `/usr/src/linux/drivers'
> make: *** [_mod_drivers] Error 2
>
> The problem seems to be that
> DRM_ERROR( "no scatter/gather memory!\n" );
>
> expands into
> printk("<3>" "[" "drm" ":%s] *ERROR* " "cannot allocate PCI GART page!\n" , ) ;
>
> I think the __FUNCTION__ changes to DRM_ERROR and friends in drmP.h
> look awfully bogus.
Nope, it's a cpp (3.0+ is fine) error - the ##args is not generated correctly when
'args...' in DRM_ERROR is empty.
marek
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-07-29 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-29 17:40 Linux 2.4.19-rc3-ac4 Alan Cox
2002-07-29 18:41 ` Stephen Lee
2002-07-29 20:46 ` Greg Louis
2002-07-29 21:07 ` mbs
2002-07-29 21:13 ` Greg Louis
2002-07-29 18:42 ` Linux 2.4.19-rc3-ac4 -build error! mbs
2002-07-29 20:44 ` Linux 2.4.19-rc3-ac4 Erik Andersen
2002-07-29 20:51 ` Grendel [this message]
2002-07-29 21:04 ` Erik Andersen
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=20020729205147.GB1722@thanes.org \
--to=grendel@thanes.org \
--cc=alan@redhat.com \
--cc=andersen@codepoet.org \
--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.