mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Baehr <mike@conio.net>
To: Marcus Hartig <m.f.h@web.de>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm4
Date: Mon, 12 Apr 2004 21:47:18 -0500	[thread overview]
Message-ID: <0cfc7cc572bd097ba649861b6eb5f91c@localhost.localdomain> (raw)
In-Reply-To: <407B00AE.7010306@web.de>

On 2004-04-12 15:48:46 -0500 Marcus Hartig <m.f.h@web.de> wrote:

> Sam Ravnborg wrote:
> 
>> I would not be suprised if NVIDIA (and wmware for that matter) takes 
>> some
>> assumptions which it should not. But I need to find out why it break,
>> and for that I need more information!
> 
> Yes. I had cut off the whole nVidia install tree. The GLX driver are 
> working, 
> but only the kernel module is in /usr/src/nv eg. I change to this dir 
> and 
> type "make install" then the Makefile.kbuild for 2.6 tries to build 
> it 
> against an 2.6 kernel. Goes with all included -mm3 and others here.
> 
> LD [M]  /usr/src/nv/nvidia.o
> /bin/sh: line 1: /usr/src/nv/.tmp_versions/nvidia.mod: No such file 
> or 
> directory  Building modules, stage 2.
> make[1]: Leaving directory `/usr/src/linux-2.6.5-mm4'
> nvidia.ko failed to build!
> make: *** [module] Error 1
> 
> strace gives not more.
> Also when I set KBUILD_EXTMOD=/usr/src/nv or to new
> 
> KBUILD_PARAMS := -C $(KERNEL_SOURCES) M=$(PWD)
> 
> in the Makefile of the nVidia source, I get this error above. Hmm.
> 
> Marcus
> -

I had these problems building nvidia driver and vmware drivers today 
after I upgraded to mm4 (with love-sources patchset as well).  I 
traced them down to a single change in the kernel Makefile which, 
after I reversed it, allowed the modules to successfully build (and my 
-mm4 kernel is happily tainted with them right now).

-export MODVERDIR := .tmp_versions
+export MODVERDIR := $(if 
$(KBUILD_EXTMOD),$(KBUILD_EXTMOD)/).tmp_versions
+                .tmp_kallsyms* .tmp_version .tmp_vmlinux*

Likely the problem _is_ nvidia and vmware coders making assumptions 
that they should not.  In any case, I'm glad to see others are 
noticing this problem and it will probably be fixed soon.

This is the sort of error I was getting with nvidia (done manually for 
clarity):

21:45:09 <@root|/usr/src/linux> 
SUBDIRS=/usr/src/archives/nvidia/NVIDIA-Linux-x86-1.0-5336-pkg1/usr/src/nv/ 
make modules
< bunch of text... compiling, etc... >
   LD [M]  
/usr/src/archives/nvidia/NVIDIA-Linux-x86-1.0-5336-pkg1/usr/src/nv//nvidia.o
/bin/sh: line 1: 
/usr/src/archives/nvidia/NVIDIA-Linux-x86-1.0-5336-pkg1/usr/src/nv//.tmp_versions/nvidia.mod: 
No such file or directory

Similar error with vmware (and I don't feel like going through the 
work of reproducing it atm XD)

Cheers,

Mike


  reply	other threads:[~2004-04-13  2:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-12 19:19 2.6.5-mm4 Marcus Hartig
2004-04-12 19:35 ` 2.6.5-mm4 Marc-Christian Petersen
2004-04-12 19:52   ` 2.6.5-mm4 Sam Ravnborg
2004-04-12 19:56 ` 2.6.5-mm4 Sam Ravnborg
2004-04-12 20:15   ` 2.6.5-mm4 Andrew Vasquez
2004-04-13  4:54     ` 2.6.5-mm4 Sam Ravnborg
2004-04-12 20:48   ` 2.6.5-mm4 Marcus Hartig
2004-04-13  2:47     ` Michael Baehr [this message]
2004-04-13  4:58     ` 2.6.5-mm4 Sam Ravnborg
  -- strict thread matches above, loose matches on Subject: below --
2004-04-13 15:22 2.6.5-mm4 Andrew Vasquez
2004-04-11  3:05 2.6.5-mm4 Andrew Morton
2004-04-12  6:46 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12  7:42   ` 2.6.5-mm4 Andrew Morton
2004-04-12  8:22     ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12  8:28       ` 2.6.5-mm4 Andrew Morton
2004-04-12  9:10         ` 2.6.5-mm4 Paul P Komkoff Jr

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=0cfc7cc572bd097ba649861b6eb5f91c@localhost.localdomain \
    --to=mike@conio.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.f.h@web.de \
    --cc=sam@ravnborg.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®