Re: scripts/mod/modpost: No such file or directory

["J�nos Hol�nyi" <csani at lme dot linux dot hu>]

On Wed, 16 Nov 2005 12:22:38 +0100, Flavio Stanchina wrote
> János Holányi wrote:
> > The kernel is fresh stock Debian 2.6.14-1-686
> > The config is an untouched /boot/config-2.6.14-1-686
> > [...]
> > /bin/sh: scripts/mod/modpost: No such file or directory
>
> The kernel sources you are using are incomplete, broken or not
> configured properly.

That should be a grave bug in the Debian BTS if that's the case (but it's not
- read on). ;)

> > Wtf is that modpost? :)
>
> It's a tool that postprocesses module symbol versions.

Thanks!

> > The relevant full output:
> >
> > /usr/bin/make -C /usr/src/linux SUBDIRS=/usr/src/modules/fglrx modules
> > make[2]: Entering directory `/home/linux-source-2.6.14'
>
> How can it be that you said "/usr/src/linux" and it goes into
> "/home/linux-source-2.6.14" ? Then "/usr/src/linux" is a symlink? Who
> created it?

I unpacked the kernel tar.bz2 into /home as I didn't have enough space in
/usr/src's file system. Symlink shouldn't case (haven't caused) any problems I
believe:
/usr/src/linux is a symlink to /home/linux-source-2.6.14

> Is that kernel tree properly configured?

Yes. Among others, I did the step-by-step instructions on your site (including
make-kpkg (my blabla of append and added) configure
(I didn't specify '--configure old' because I am using
/boot/config-2.6.14-1-686 and there is no old config)

> If you're using a stock 2.6.14-1-686 kernel, why aren't you using
> kernel-headers-2.6.14-1-686 instead of the full kernel source? As in:
>   $ sudo apt-get install linux-headers-2.6.14-1-686
>   $ cd /usr/src/linux-headers-2.6.14-1-686
>   $ make SUBDIRS=/usr/src/modules/fglrx modules

...because I like leaving the option to (un)patch the kernel (testing
patches), hack the config and recompile at any time (and I also like using
make-kpkg). I am, however, only using those temporarily. I use a stock kernel.
Sometimes I also compile image debs for external machines here. That's why I
haven't used two method but only one at all times: kernel-tree (and nowadays
linux-tree)

On the other hand, you've got a valid point since recompiling fglrx happens
more often, so I think I'll give linux-headers a try and it could easily
happen that I will be also using it instead of the full kernel source.
However it seems like I cannot build deb module packages by using the
linux-headers package - is this correct?

----
By the way:
The only way I could compile the fglrx module .deb this time was recompiling
the whole stock kernel (make-kpkg blabla kernel_image modules_image)
----

> (if you didn't try that because my page still says that fglrx doesn't
> build with kernel-headers, I apologize)

I did try also with linux-headers but I got the same error.
I'll give it another try soon - currently there's a network problem and I
cannot download&install linux-headers package right now.

Thanks anyway.

Regs,
Csani

--
Debian Project (http://www.debian.org/)