From: Garnet MacPhee <garnet-vVazHDhchvNCCzmm7wA0Mw@public.gmane.org>
To: Pekka Paalanen <pq-X3B1VOXEql0@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: Cannot compile nouveau.o in drm with kernel 2.6.26
Date: Sat, 19 Jul 2008 05:42:41 -0600 [thread overview]
Message-ID: <4881D331.3070901@signalpeak.net> (raw)
In-Reply-To: <20080719103932.7a35029e@ct200006>
Pekka Paalanen wrote:
> On Fri, 18 Jul 2008 18:22:47 -0600
> Garnet MacPhee <garnet-vVazHDhchvNCCzmm7wA0Mw@public.gmane.org> wrote:
>
>> I am getting the following error when trying to compile nouveau.o in drm/linux-core on linux kernel 2.6.26. Drm itself
>
> By "Drm itself" I assume you are referring to libdrm.
Yes, thats right.
>
>
>> root@default:~/drm/linux-core# make nouveau.o
>> make DRM_MODULES=nouveau.o modules
>> make[1]: Entering directory `/root/drm/linux-core'
>> make -C /lib/modules/2.6.26/source SUBDIRS=`pwd` DRMSRCDIR=`pwd` modules
>> make[2]: Entering directory `/usr/src/linux-2.6.26'
>> CC [M] /root/drm/linux-core/drm_auth.o
>> In file included from include/linux/gfp.h:4,
>> from include/linux/slab.h:12,
>> from include/linux/percpu.h:5,
>> from include/asm/local.h:4,
>> from include/linux/module.h:19,
>> from /root/drm/linux-core/drmP.h:44,
>> from /root/drm/linux-core/drm_auth.c:36:
>> include/linux/mmzone.h:18:26: error: linux/bounds.h: No such file or directory
>> include/linux/mmzone.h:197:5: warning: "MAX_NR_ZONES" is not defined
>> In file included from include/linux/gfp.h:4,
>> from include/linux/slab.h:12,
>> from include/linux/percpu.h:5,
>> from include/asm/local.h:4,
>> from include/linux/module.h:19,
>> from /root/drm/linux-core/drmP.h:44,
>> from /root/drm/linux-core/drm_auth.c:36:
>> include/linux/mmzone.h:218: error: 'MAX_NR_ZONES' undeclared here (not in a function)
>> In file included from include/asm/pci.h:4,
>> from include/linux/pci.h:948,
>> from /root/drm/linux-core/drmP.h:51,
>> from /root/drm/linux-core/drm_auth.c:36:
>> include/linux/mm.h:429:63: warning: "NR_PAGEFLAGS" is not defined
>
> These look funny. Did you build your kernel from the same source tree
> the DRM is using (/lib/modules/2.6.26/source)?
Yes, /lib/modules/2.6.26/source is actually a pointer, and it points to /usr/src/linux-2.6.26 just like it should.
> I haven't seen these errors before, but my first guess would be an
> unconfigured or never-compiled kernel source tree. Hmm, yes, at least
> include/linux/bounds.h is a build-time generated file.
>
> If you are using a precompiled kernel image from your favourite
> distribution, you might need to install also another package which allows
> building custom kernel modules. This is distro specific.
>
I am running Slackware 12.1, and I compile my own custom kernel, I do not use the precompiled ones (they are 2.6.24 vintage).
The kernel has indeed been compiled, and I can run X using the nv driver.
Also, the same drm git will build correctly with kernel 2.6.25.
next prev parent reply other threads:[~2008-07-19 11:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 0:22 Cannot compile nouveau.o in drm with kernel 2.6.26 Garnet MacPhee
[not found] ` <488133D7.7050808-vVazHDhchvNCCzmm7wA0Mw@public.gmane.org>
2008-07-19 7:39 ` Pekka Paalanen
2008-07-19 11:42 ` Garnet MacPhee [this message]
2008-07-19 13:55 ` Garnet MacPhee
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=4881D331.3070901@signalpeak.net \
--to=garnet-vvazhdhchvncczmm7wa0mw@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=pq-X3B1VOXEql0@public.gmane.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.