Skip to contentSkip to conversation

2.4.0-ac6: mm/vmalloc.c compile error

PATCH New Frank Davis 3 participants 3 messages Jan 11, 2001 vmalloc

lore
Share & tools
lore
#0 lore raw

Hello,
The following error occurred while compiling 2.4.0-ac6..The strange
thing is that I checked mm/vmalloc.c (line 188, and the entire file) and didn't see PKMAP_BASE mentioned. My guess is that there is a problem with one of the header files.

Regards,
Frank

vmalloc.c: In function `get_vm_area':
vmalloc.c:188: `PKMAP_BASE' undeclared (first use in this function) vmalloc.c:188: (Each undeclared identifier is reported only once vmalloc.c:188: for each function it appears in.) make[2]: *** [vmalloc.o] Error 1
make[2]: Leaving directory `/usr/src/linux/mm'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux/mm'
make: *** [_dir_mm] Error 2

#1 lore raw

PATCH 1/1 highmem-2.4.0-A0 (was: Re: 2.4.0-ac6: mm/vmalloc.c compile error)

Quoted 5 lines · Frank Davis

Hello,
The following error occurred while compiling 2.4.0-ac6. [...]

vmalloc.c: In function `get_vm_area':
vmalloc.c:188: `PKMAP_BASE' undeclared (first use in this function)

you are compiling with HIGHMEM enabled (which makes sense only if you have more than ~900MB RAM), and i accidentally broke HIGHMEM with the vmalloc fix in -pre1/-ac5. The attached patch fixes it.

Ingo

include/linux/vmalloc.h renamed from include/linux/vmalloc.h.orig +1 -0
@@ -4,6 +4,7 @@
 #include <linux/sched.h>
 #include <linux/mm.h>
 #include <linux/spinlock.h>
+#include <linux/highmem.h>
 
 #include <asm/pgtable.h>
 
#2 lore raw
In reply to Frank Davis
Quoted 4 lines

The following error occurred while compiling 2.4.0-ac6..The strange
thing is that I checked mm/vmalloc.c (line 188, and the entire file) and didn't see PKMAP_BASE mentioned. My guess is that there is a problem with one of the header files.

Its defined in asm/highmem.h/ Probabyl a missing include if building a bigmem kenrel

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/