From: Kaoru Fukui <k_fukui@highway.ne.jp>
To: linuxppc-dev@lists.linuxppc.org
Cc: k_fukui@highway.ne.jp
Subject: linux-2.5.7 problem
Date: Mon, 25 Mar 2002 18:58:22 +0900 (JST) [thread overview]
Message-ID: <200203251001.TAA12917@mail.highway.ne.jp> (raw)
Hi!
I got this problem.
sched.h of linux-2.5.7 doesn't has p_pptr. but sched.h of linux-2.4 has it.
Should I use parent instead of p_pptr ?
Kaoru
-------
gcc -D__KERNEL__ -I/usr/src/redhat/BUILD/linux/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -I/usr/src/redhat/BUILD/linux/arch/ppc -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized -mmultiple -mstring -DKBUILD_BASENAME=signal -c -o signal.o signal.c
signal.c: In function `do_signal':
signal.c:597: structure has no member named `p_pptr'
signal.c:598: structure has no member named `p_pptr'
signal.c:637: structure has no member named `p_pptr'
make[1]: *** [signal.o] 1
make[1]: `/usr/src/redhat/BUILD/linux/arch/ppc/kernel'
---linux-2.4 sched.h
/*
* pointers to (original) parent process, youngest child, younger sibling,
* older sibling, respectively. (p->father can be replaced with
* p->p_pptr->pid)
*/
struct task_struct *p_opptr, *p_pptr, *p_cptr, *p_ysptr, *p_osptr;
struct list_head thread_group;
---linux-2.5.7 sched.h
/*
* pointers to (original) parent process, youngest child, younger sibling,
* older sibling, respectively. (p->father can be replaced with
* p->parent->pid)
*/
struct task_struct *real_parent; /* real parent process (when being debugged) */
struct task_struct *parent; /* parent process */
struct list_head children; /* list of my children */
struct list_head sibling; /* linkage in my parent's children list */
struct list_head thread_group;
/* PID hash table linkage. */
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2002-03-25 9:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200203251001.TAA12917@mail.highway.ne.jp \
--to=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).