-- Forwarded Message --
Subject: Re: [kbuild-devel] Doubt what is the difference of compiling module
in SuSE and Redhad , Mandrake
Date: Monday 09 May 2005 12:20
From: karthik <[EMAIL PROTECTED]>
To: Andreas Gruenbacher <[EMAIL PROTECTED]>
Sir,
I have written a shell s
On Mon, May 09, 2005 at 10:03:21AM -0700, karthik r wrote:
> Hi ,
>
> But the problem with me is that we cannot release the source code.
That does not in any way prevent you from creating a Makefile according
to text in modules.txt?
Or is it so that you only have access to the .o file and no
Hi ,
But the problem with me is that we cannot release the source code.
That's why I am converting my module to test.o in my system itself and
trying to write some shell script to convert it to target test.ko, so
that script is executed in target system my module can be loaded.
Karthik
---
On Sun, May 08, 2005 at 08:20:50PM +0200, Sam Ravnborg wrote:
> > Shouldn't kconfig exit with an error if a not available symbol gets
> > selected?
> No. There are meny configurations where we select a symbol that is
> only visible in some configurations.
>
> Several possibilities exists:
> 1) Sil
karthik,
On Sunday 08 May 2005 20:16, Sam Ravnborg wrote:
> > In 2.6 kernel a module compiled in one version(say 2.6.4) of SuSE
> > is not loading in another version(say 2.6.8) of SuSE, even when we
> > convert the module.o to module.ko in the latest version of SUSE.
forget trying to use a
> Shouldn't kconfig exit with an error if a not available symbol gets
> selected?
No. There are meny configurations where we select a symbol that is
only visible in some configurations.
Several possibilities exists:
1) Silently ignore SELECT SYMBOL when SYMBOL is undefined
2) Warn - as we do today
On Fri, May 06, 2005 at 12:27:12PM -0700, karthik wrote:
> Hi ,
>
> Can anybody tell me what is the difference in compiling a module in
> SuSE distribution and other LInux distribution like Redhad or Mandrake.
>
> In 2.6 kernel a module compiled in one version(say 2.6.4) of SuSE
