From: Remco Post <r.post@sara.nl>
To: "Oliver Pitzeier" <o.pitzeier@uptime.at>
Cc: thunder@lightweight.ods.org, donaldlf@cs.rose-hulman.edu,
axp-kernel-list@redhat.com, linux-kernel@vger.kernel.org,
ink@jurassic.park.msu.ru
Subject: [PATCH] include/linux/ptrace.h Re: Kernel 2.5.33 compile errors (Re: Kernel 2.5.33 successfully compiled)
Date: Wed, 4 Sep 2002 00:22:43 +0200 [thread overview]
Message-ID: <20020904002243.7d3a4412.r.post@sara.nl> (raw)
In-Reply-To: <200209031827.16594.o.pitzeier@uptime.at>
[-- Attachment #1: Type: text/plain, Size: 5429 bytes --]
I now do have a successful compile, will try to boot it in a sec.... This is from the linuxppc-2.5 tree, will do the same patches on Linus' tree to see if that compiles as well. Ok, it sort of boots as well:
Kernel command line: console=ttyS0,9600 console=tty0 root=/dev/sda2
time_init: decrementer frequency = 16.666782 MHz
Calibrating delay loop... 266.24 BogoMIPS
Memory: 62280k available (1568k kernel code, 804k data, 100k init, 0k highmem)
Security Scaffold v1.0.0 initialized
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes)
Inode-cache hash table entries: 4096 (order: 3, 32768 bytes)
Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing RT netlink socket
PCI: Probing PCI hardware
Oops: kernel access of bad area, sig: 11
NIP: C000EFA0 LR: C00DF404 SP: C0363B50 REGS: c0363aa0 TRAP: 0301 Not taintedMSR: 00001032 EE: 0 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000000, DSISR: 42000000
TASK = c0360040[1] 'swapper' Last syscall: 120
last math 00000000 last altivec 00000000
GPR00: C75C0080 C0363B50 C0360040 C03F94C0 00000000 0000000E 00000001 C0363B78
GPR08: 00000000 00000000 C03F94CC C75C0000 64676500
Call backtrace:
C00DF404 C00E026C C00E036C C00E057C C020F130 C020C5F4 C020C638
C00038E0 C0008A3C
Kernel panic: Attempted to kill init!
Remember this is a prep board....
On Tue, 3 Sep 2002 18:27:16 +0200
"Oliver Pitzeier" <o.pitzeier@uptime.at> wrote:
> On Tuesday 03 September 2002 18:18, Oliver Pitzeier wrote:
> > On Tuesday 03 September 2002 18:14, Thunder from the hill wrote:
> [ ... ]
> > No. It seems simply missing. In 2.5.32 it is there. On the right place.
> > :o))))
> >
> > > > > process.c: In function `alpha_clone':
> > > > > process.c:268: too few arguments to function `do_fork'
> > > > > process.c: In function `alpha_vfork':
> > > > > process.c:277: too few arguments to function `do_fork'
> > > > > make[1]: *** [process.o] Error 1
> > > > > make[1]: Leaving directory
> > >
> > > Yes, the syntax changed.
>
> OK, after calling do_fork with "NULL" as extra argument. It compiles.
>
> (No, I do not want to make the kernel run fine [currently], but I want to
> trace down the count of bugs to a countable value. :o) )
>
> [ ... ]
>
> OK. The next problem seems harded to me (Maybe Ivan can help a bit!?):
>
Attached patch worked for _compiling_ on my powermac, it might help for you as well....
> gcc -Wp,-MD,./.irq.o.d -D__KERNEL__ -I/usr/src/linux-2.5.33/include -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer
> -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -msmall-data
> -mcpu=ev5 -Wa,-mev6 -nostdinc -iwithprefix include -DKBUILD_BASENAME=irq
> -c -o irq.o irq.c
> In file included from irq.c:15:
> /usr/src/linux-2.5.33/include/linux/ptrace.h:28: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:28: warning: its scope is only
> this definition or declaration, which is probably not what you want
> /usr/src/linux-2.5.33/include/linux/ptrace.h:29: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:30: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:31: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:32: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:33: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:35: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:36: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h:39: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h: In function `ptrace_link':
> /usr/src/linux-2.5.33/include/linux/ptrace.h:41: dereferencing pointer to
> incomplete type
> /usr/src/linux-2.5.33/include/linux/ptrace.h:42: warning: passing arg 1 of
> `__ptrace_link' from incompatible pointer type
> /usr/src/linux-2.5.33/include/linux/ptrace.h:42: warning: passing arg 2 of
> `__ptrace_link' from incompatible pointer type
> /usr/src/linux-2.5.33/include/linux/ptrace.h: At top level:
> /usr/src/linux-2.5.33/include/linux/ptrace.h:44: warning: `struct task_struct'
> declared inside parameter list
> /usr/src/linux-2.5.33/include/linux/ptrace.h: In function `ptrace_unlink':
> /usr/src/linux-2.5.33/include/linux/ptrace.h:46: dereferencing pointer to
> incomplete type
> /usr/src/linux-2.5.33/include/linux/ptrace.h:47: warning: passing arg 1 of
> `__ptrace_unlink' from incompatible pointer type
> make[1]: *** [irq.o] Error 1
> make[1]: Leaving directory `/usr/src/linux-2.5.33/arch/alpha/kernel'
> make: *** [arch/alpha/kernel] Error 2
>
> --
> Oliver Pitzeier
> UNIX Administrator
> -
> Linux 2.4.19 i686 Load: 0.32 0.25 0.27
>
> -
> 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/
[-- Attachment #2: ptrace.patch --]
[-- Type: application/octet-stream, Size: 406 bytes --]
*** ptrace.h.org Tue Sep 3 15:14:35 2002
--- ptrace.h Tue Sep 3 20:31:13 2002
***************
*** 24,29 ****
--- 24,30 ----
#define PTRACE_SYSCALL 24
#include <asm/ptrace.h>
+ #include <linux/sched.h>
extern int ptrace_readdata(struct task_struct *tsk, unsigned long src, char *dst, int len);
extern int ptrace_writedata(struct task_struct *tsk, char * src, unsigned long dst, int len);
next prev parent reply other threads:[~2002-09-03 22:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 10:59 Kernel 2.5.33 successfully compiled Oliver Pitzeier
2002-09-03 11:57 ` Oliver Pitzeier
2002-09-03 15:08 ` Leslie Donaldson
2002-09-03 15:26 ` Padraig Brady
2002-09-03 15:53 ` Oliver Pitzeier
2002-09-03 16:14 ` Thunder from the hill
2002-09-03 16:18 ` Oliver Pitzeier
2002-09-03 16:27 ` Kernel 2.5.33 compile errors (Re: Kernel 2.5.33 successfully compiled) Oliver Pitzeier
2002-09-03 16:39 ` Thunder from the hill
2002-09-03 22:22 ` Remco Post [this message]
2002-09-03 22:37 ` [PATCH] include/linux/ptrace.h " Thunder from the hill
2002-09-04 7:33 ` Remco Post
2002-09-04 9:25 ` Leslie Donaldson
2002-09-04 16:24 ` Leslie Donaldson
2002-09-04 21:41 ` Leslie Donaldson
2002-09-03 16:34 ` Kernel 2.5.33 successfully compiled Thunder from the hill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020904002243.7d3a4412.r.post@sara.nl \
--to=r.post@sara.nl \
--cc=axp-kernel-list@redhat.com \
--cc=donaldlf@cs.rose-hulman.edu \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=o.pitzeier@uptime.at \
--cc=thunder@lightweight.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome