Hi Folks,
Here's the solution we have found:
With the latest SuSE 2.6.5-7.75 kernel sources:
The problem is that /lib/modules/2.6.5-7.75/build points to
/usr/src/linux-2.6.5-7.75-obj which is some kind of wierd directory
that has:
. .. bigsmp debug default out smp
So simply removing this symlink and putting back a link to
/usr/src/linux-2.6.5-7.75 fixes our problems.
So the question is who is at fault here?. We used KBUILD to
build our modules and obviously the build link in /lib/modules/<kernel>/build
isn't pointing to the correct source tree.
best regards
Dev Mazumdar
---------------------------------------------------------------------
4Front Technologies
4035 Lafayette Place, Unit F, Culver City, CA 90232, USA
Tel: 310 202 8530 Fax: 310 202 0496 URL: http://www.opensound.com
---------------------------------------------------------------------
> Here's the solution we have found:
>
> With the latest SuSE 2.6.5-7.75 kernel sources:
>
> The problem is that /lib/modules/2.6.5-7.75/build points to
> /usr/src/linux-2.6.5-7.75-obj which is some kind of wierd directory
> that has:
>
> . .. bigsmp debug default out smp
>
> So simply removing this symlink and putting back a link to
> /usr/src/linux-2.6.5-7.75 fixes our problems.
>
> So the question is who is at fault here?. We used KBUILD to
> build our modules and obviously the build link in /lib/modules/<kernel>/build
> isn't pointing to the correct source tree.
I don't know if this is the solution to your problem, but /usr/src/linux/README.SUSE
says
(3) Compile the module(s) by changing into the module source directory
and typing ``make -C /usr/src/linux
O=/usr/src/linux-obj/$ARCH/$FLAVOR M=`pwd` modules''.
Substitute $ARCH and $FLAVOR with the architecture and flavor
for which to build the module(s).
I hope this helps,
Duncan.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 17 Jun 2004, 4Front Technologies wrote:
> Hi Folks,
>
> Here's the solution we have found:
>
> With the latest SuSE 2.6.5-7.75 kernel sources:
>
> The problem is that /lib/modules/2.6.5-7.75/build points to
> /usr/src/linux-2.6.5-7.75-obj which is some kind of wierd directory
> that has:
>
> . .. bigsmp debug default out smp
>
> So simply removing this symlink and putting back a link to
> /usr/src/linux-2.6.5-7.75 fixes our problems.
>
> So the question is who is at fault here?. We used KBUILD to
> build our modules and obviously the build link in /lib/modules/<kernel>/build
> isn't pointing to the correct source tree.
IF the fault here is SUSE's, then submit THEM a bug report and stop whining in lkml.
If you did your homework in the first place you would see that that's not a
Linux Kernel problem and would not start this whole discussion.
All you've managed with this was ening with any reputation 4Front Technologies
could have between lkml readers.
Mind Booster Noori
- --
/* ************************************************************************* */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email and Microsoft attachments.
/\ Software patents are endangering the computer industry all around the world.
Join the LPF: http://lpf.ai.mit.edu/ http://petition.eurolinux.org/
/* ************************************************************************* */
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFA0s43mNlq8m+oD34RAgx8AKDKlRG8j8ik3LFsjKDKsY4TnVkDcgCfUCoV
gajxf21QF9lJfYNW37d19Wg=
=eZ8j
-----END PGP SIGNATURE-----