From: Adrian Bunk <bunk@stusta.de>
To: Luca Falavigna <dktrkranz@gmail.com>
Cc: dri-devel@lists.sourceforge.net, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] Compile bug in Direct Rendering Manager (kernel 2.6.11-rc1)
Date: Fri, 14 Jan 2005 00:29:43 +0100 [thread overview]
Message-ID: <20050113232943.GO29578@stusta.de> (raw)
In-Reply-To: <41E6525E.6030200@gmail.com>
On Thu, Jan 13, 2005 at 11:50:06AM +0100, Luca Falavigna wrote:
>
> While compiling kernel 2.6.11-rc1, make exits with a lot of errors concerning
> Direct Rendering Manager. Here is some info I've grabbed:
>
> [...]
> CC [M] drivers/char/drm/gamma_drv.o
> drivers/char/drm/gamma_drv.c:39:22: drm_auth.h: No such file or directory
>...
> make[3]: *** [drivers/char/drm/gamma_drv.o] Error 1
>...
> [...]
> CONFIG_DRM=m
> CONFIG_DRM_TDFX=m
> CONFIG_DRM_GAMMA=m
>...
The more interestion options would have been:
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
If you answer "yes" to
"Prompt for development and/or incomplete code/drivers"
and "no" to
"Select only drivers expected to compile cleanly"
it souldn't be a big surprise if a driver doesn't compile.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-01-13 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 10:50 [BUG] Compile bug in Direct Rendering Manager (kernel 2.6.11-rc1) Luca Falavigna
2005-01-13 23:29 ` Adrian Bunk [this message]
2005-01-13 23:50 ` Jon Smirl
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=20050113232943.GO29578@stusta.de \
--to=bunk@stusta.de \
--cc=dktrkranz@gmail.com \
--cc=dri-devel@lists.sourceforge.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 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.