* Build problems 2.4.4 on SPARC
@ 2001-05-02 22:22 Marc Evans
0 siblings, 0 replies; 2+ messages in thread
From: Marc Evans @ 2001-05-02 22:22 UTC (permalink / raw)
To: linux-kernel
Hello -
While trying to compile the 2.4.4 kernel on a SPARC-20, I encounter the
following error.
[1.] One line summary of the problem:
kernel 2.4.4 won't compile
[2.] Full description of the problem/report:
See item 7.7 for details
[3.] Keywords (i.e., modules, networking, kernel):
kernel
[4.] Kernel version (from /proc/version):
2.4.1
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
[6.] A small shell script or example program which triggers the
problem (if possible)
[7.] Environment
[7.1.] Software (add the output of the ver_linux script here)
Linux SoftwareHackery.Com 2.4.1 #8 SMP Thu Feb 8 09:57:19 EST 2001 sparc unknown
Gnu C 2.95
Gnu make 3.78.1
binutils 2.9.5.0.22
util-linux 2.10f
mount 2.10f
modutils 2.3.10-pre1
e2fsprogs 1.18
PPP 2.3.11
Linux C Library 2.1.3
Dynamic linker (ldd) 2.1.3
Procps 2.0.6
Net-tools 1.54
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded
[7.2.] Processor information (from /proc/cpuinfo):
cpu : Texas Instruments, Inc. - SuperSparc-(II)
fpu : SuperSparc on-chip FPU
promlib : Version 3 Revision 2
prom : 2.25
type : sun4m
ncpus probed : 1
ncpus active : 1
Cpu0Bogo : 74.75
MMU type : TI Viking/MXCC
contexts : 65536
nocache total : 1048576
nocache used : 736512
CPU0 : online
[7.3.] Module information (from /proc/modules):
<none>
[7.4.] Loaded driver and hardware information (/proc/ioports, /proc/iomem)
<none>
[7.5.] PCI information ('lspci -vvv' as root)
pcilib: Cannot open /proc/bus/pci
lspci: Cannot find any working access method.
[7.6.] SCSI information (from /proc/scsi/scsi)
Attached devices:
Host: scsi0 Channel: 00 Id: 00 Lun: 00
Vendor: SEAGATE Model: ST15150N Rev: AV01
Type: Direct-Access ANSI SCSI revision: 02
[7.7.] Other information that might be relevant to the problem
(please look in /proc and include all information that you
think to be relevant):
[X.] Other notes, patches, fixes, workarounds:
make[1]: Entering directory `/usr/src/linux-2.4.4/mm'
make all_targets
make[2]: Entering directory `/usr/src/linux-2.4.4/mm'
gcc -D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes
-O2 -fomit-frame-pointer -fno-strict-aliasing -m32 -pipe -mno-fpu
-fcall-used-g5 -fcall-used-g7 -c -o memory.o memory.c
memory.c:183: macro `pmd_alloc' used with too many (3) args
memory.c:204: macro `pte_alloc' used with too many (3) args
memory.c:725: macro `pte_alloc' used with too many (3) args
memory.c:750: macro `pmd_alloc' used with too many (3) args
memory.c:805: macro `pte_alloc' used with too many (3) args
memory.c:832: macro `pmd_alloc' used with too many (3) args
memory.c:1339: macro `pmd_alloc' used with too many (3) args
memory.c:1342: macro `pte_alloc' used with too many (3) args
memory.c:1392: macro `pte_alloc' used with too many (3) args
memory.c: In function `copy_page_range':
memory.c:183: warning: passing arg 1 of `___f_pmd_alloc' from incompatible pointer type
memory.c:183: warning: passing arg 2 of `___f_pmd_alloc' makes integer from pointer without a cast
memory.c:204: warning: passing arg 1 of `___f_pte_alloc' from incompatible pointer type
memory.c:204: warning: passing arg 2 of `___f_pte_alloc' makes integer from pointer without a cast
memory.c: In function `zeromap_pmd_range':
memory.c:725: warning: passing arg 1 of `___f_pte_alloc' from incompatible pointer type
memory.c:725: warning: passing arg 2 of `___f_pte_alloc' makes integer from pointer without a cast
memory.c: In function `zeromap_page_range':
memory.c:750: warning: passing arg 1 of `___f_pmd_alloc' from incompatible pointer type
memory.c:750: warning: passing arg 2 of `___f_pmd_alloc' makes integer from pointer without a cast
memory.c: In function `remap_pmd_range':
memory.c:805: warning: passing arg 1 of `___f_pte_alloc' from incompatible pointer type
memory.c:805: warning: passing arg 2 of `___f_pte_alloc' makes integer from pointer without a cast
memory.c: In function `remap_page_range':
memory.c:832: warning: passing arg 1 of `___f_pmd_alloc' from incompatible pointer type
memory.c:832: warning: passing arg 2 of `___f_pmd_alloc' makes integer from pointer without a cast
memory.c: In function `handle_mm_fault':
memory.c:1339: warning: passing arg 1 of `___f_pmd_alloc' from incompatible pointer type
memory.c:1339: warning: passing arg 2 of `___f_pmd_alloc' makes integer from pointer without a cast
memory.c:1342: warning: passing arg 1 of `___f_pte_alloc' from incompatible pointer type
memory.c:1342: warning: passing arg 2 of `___f_pte_alloc' makes integer from pointer without a cast
memory.c: In function `__pmd_alloc':
memory.c:1364: warning: implicit declaration of function `pmd_alloc_one_fast'
memory.c:1364: warning: assignment makes pointer from integer without a cast
memory.c:1367: warning: implicit declaration of function `pmd_alloc_one'
memory.c:1367: warning: assignment makes pointer from integer without a cast
memory.c:1381: warning: implicit declaration of function `pgd_populate'
memory.c: At top level:
memory.c:1393: conflicting types for `___f_pte_alloc' /usr/src/linux-2.4.4/include/asm/pgalloc.h:125: previous declaration of `___f_pte_alloc' memory.c: In function `___f_pte_alloc':
memory.c:1398: warning: implicit declaration of function `pte_alloc_one_fast'
memory.c:1398: `address' undeclared (first use in this function)
memory.c:1398: (Each undeclared identifier is reported only once
memory.c:1398: for each function it appears in.)
memory.c:1398: warning: assignment makes pointer from integer without a cast
memory.c:1401: warning: implicit declaration of function `pte_alloc_one'
memory.c:1401: warning: assignment makes pointer from integer without a cast
memory.c:1415: warning: implicit declaration of function `pmd_populate'
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Build problems 2.4.4 on SPARC
[not found] <mailman.988827960.5573.linux-kernel2news@redhat.com>
@ 2001-05-03 0:14 ` Pete Zaitcev
0 siblings, 0 replies; 2+ messages in thread
From: Pete Zaitcev @ 2001-05-03 0:14 UTC (permalink / raw)
To: Marc, linux-kernel
> While trying to compile the 2.4.4 kernel on a SPARC-20, I encounter the
> following error.
> make[1]: Entering directory `/usr/src/linux-2.4.4/mm'
> make all_targets
> make[2]: Entering directory `/usr/src/linux-2.4.4/mm'
> gcc -D__KERNEL__ -I/usr/src/linux-2.4.4/include -Wall -Wstrict-prototypes
> -O2 -fomit-frame-pointer -fno-strict-aliasing -m32 -pipe -mno-fpu
> -fcall-used-g5 -fcall-used-g7 -c -o memory.o memory.c
> memory.c:183: macro `pmd_alloc' used with too many (3) args
Known problem... For some reason, even current vger CVS has it.
You might want to try Eirik's patch, but I have not idea if
it is correct.
http://marc.theaimsgroup.com/?l=linux-sparc&m=98731698113169&w=2
IMHO, sparc needs a port maintainer. Obviously, DaveM has barely
enough time to deal with sparc64. Unfortunately it is not a position
for weak (like myself). At various times I, Uzi, and Anton tried
that crown for size, but it is way too big and heavy.
-- Pete
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2001-05-03 0:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <mailman.988827960.5573.linux-kernel2news@redhat.com>
2001-05-03 0:14 ` Build problems 2.4.4 on SPARC Pete Zaitcev
2001-05-02 22:22 Marc Evans
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox