All of lore.kernel.org
 help / color / mirror / Atom feed
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 07:55:34 -0600	[thread overview]
Message-ID: <4881F256.3030303@signalpeak.net> (raw)
In-Reply-To: <20080719103932.7a35029e@ct200006>

OK, I found the problem.

Running 'make clean' after compiling 2.6.26 will remove /usr/src/linux-2.6.26/include/linux/bounds.h. This is a change in 
behavior from 2.6.25 and earlier kernels.

I have always run 'make clean' (NOT make mrproper) after compiling a kernel, more out of habit than anything else, I guess. It 
never caused a problem before.

I am now happily running nouveau on kernel 2.6.26. Sorry about making noise on the list, but hopefully this will save somebody 
some time and hassle. I don't know what the long term solution should be, whether 'make clean' should be changed back to its 
previous behavior, whether drivers should stop referencing bounds.h, or whether people just have to change their behavior and 
not run 'make clean' after compiling.

      parent reply	other threads:[~2008-07-19 13:55 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
2008-07-19 13:55     ` Garnet MacPhee [this message]

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=4881F256.3030303@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.