On Wed, Jul 20, 2005 at 02:59:34PM -0400, ashwin tanugula wrote:
> Hi,
> I am working on the UML/PPC port and I got the following errors. Can
> anybody tell me how to solve the ptrace_link and ptrace_unlink errors
> in linux/ptrace.h file?

>   CC      arch/um/util/mk_task_kern.o
> In file included from include/asm/arch/user.h:7,
>                  from include/asm/processor-i386.h:20,
>                  from include/asm/processor-generic.h:17,
>                  from include/asm/processor.h:11,
>                  from include/asm/thread_info.h:11,
>                  from include/linux/thread_info.h:21,
>                  from include/linux/spinlock.h:12,
>                  from include/linux/capability.h:45,
>                  from include/linux/sched.h:7,
>                  from arch/um/util/mk_task_kern.c:1:

First of all, there's something very wrong when you're trying to build
UML/ppc and you're pulling in include/asm/processor-i386.h.  Somehow,
your pool is corrupted by a previous i386 build.

Second, this is caused by a recursive include, where include/asm-ppc
is including linux/ptrace.h, which is trying to include sched.h.
We're in the middle of sched.h, so the that include doesn't happen,
but the task struct hasn't been defined yet in the outer sched.h so
the references to it fail.

The fix is to break this include chain somehow (after fixing the
processor-i386 thing).  Find one of those includes which is unecessary
(hopefully in UML code) and remove it.

                                Jeff


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
User-mode-linux-user mailing list
User-mode-linux-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user

Reply via email to