Re: [PATCH]Problems with compling 2.4.14 on SMP and kernel versioning on modules set.

BALBIR SINGH (balbir.singh@wipro.com)
Thu, 08 Nov 2001 18:17:53 +0530


This is a multi-part message in MIME format.

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Found another one in md.h

*** md.h.org Thu Nov 8 17:56:38 2001
--- md.h Thu Nov 8 17:56:50 2001
***************
*** 26,32 ****
#include <linux/ioctl.h>
#include <linux/types.h>
#include <asm/bitops.h>
- #include <linux/module.h>
#include <linux/hdreg.h>
#include <linux/proc_fs.h>
#include <linux/smp_lock.h>
--- 26,31 ----
***************
*** 35,40 ****
--- 34,40 ----
#include <linux/random.h>
#include <linux/locks.h>
#include <linux/kernel_stat.h>
+ #include <linux/module.h>
#include <asm/io.h>
#include <linux/completion.h>

Balbir

BALBIR SINGH wrote:

> I could not compile a UP (non-SMP) kernel on my system, with module
> versioning set, the problem was traced to ksyms.c
>
> * Herein lies all the functions/variables that are "exported" for linkage
> * with dynamically loaded kernel modules.
> * Jon.
> *
>
> Now linux/module.h is included in ksyms.c
>
> Below is a patch for compiling a NON-SMP kernel in 2.4.14. If this is
> correct, please apply. In this patch, the include of linux/module.h
> (which redifines smp_num_cpus based on kernel versioning) has been moved
> below the include of linux/kernel_stat.h
>
>
> --- ksyms.c Thu Nov 8 17:41:39 2001
> +++ ksyms.c.org Thu Nov 8 16:41:48 2001
> @@ -9,12 +9,12 @@
> * by Bjorn Ekwall <bj0rn@blox.se>
> */
>
> -#include <linux/blkdev.h>
> -#include <linux/cdrom.h>
> -#include <linux/kernel_stat.h>
> #include <linux/config.h>
> #include <linux/slab.h>
> #include <linux/module.h>
> +#include <linux/blkdev.h>
> +#include <linux/cdrom.h>
> +#include <linux/kernel_stat.h>
> #include <linux/vmalloc.h>
> #include <linux/sys.h>
> #include <linux/utsname.h>
>
>
>
>------------------------------------------------------------------------
>
>-------------------------------------------------------------------------------------------------------------------------
>Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
>is intended for use only by the individual or entity to which it is
>addressed, and may contain information that is privileged, confidential or
>exempt from disclosure under applicable law. If you are not the intended
>recipient or it appears that this mail has been forwarded to you without
>proper authority, you are notified that any use or dissemination of this
>information in any manner is strictly prohibited. In such cases, please
>notify us immediately at mailto:mailadmin@wipro.com and delete this mail
>from your records.
>----------------------------------------------------------------------------------------------------------------------
>

--------------InterScan_NT_MIME_Boundary
Content-Type: text/plain;
name="InterScan_Disclaimer.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="InterScan_Disclaimer.txt"

-------------------------------------------------------------------------------------------------------------------------
Information transmitted by this E-MAIL is proprietary to Wipro and/or its Customers and
is intended for use only by the individual or entity to which it is
addressed, and may contain information that is privileged, confidential or
exempt from disclosure under applicable law. If you are not the intended
recipient or it appears that this mail has been forwarded to you without
proper authority, you are notified that any use or dissemination of this
information in any manner is strictly prohibited. In such cases, please
notify us immediately at mailto:mailadmin@wipro.com and delete this mail
from your records.
----------------------------------------------------------------------------------------------------------------------

--------------InterScan_NT_MIME_Boundary--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/