RE: Error compiling for java

["Goel, Mudit (Mudit)" <muditg at alcatel-lucent dot com>]

Is there a way to restart the build from the place where it encountered
errors or is it that we have to start it afresh each time.

-----Original Message-----
From: Andrew Haley [mailto:aph@redhat.com]
Sent: Wednesday, December 13, 2006 3:21 PM
To: Goel, Mudit (Mudit)
Cc: 'java@gcc.gnu.org'
Subject: Re: Error compiling for java


Goel, Mudit (Mudit) writes:
 > All,
 >   I am trying to get a java cross compiler to be used with ppc750. 
 >   I am using dem0-ppc750.sh  .This is a partial build output that I got.
 > Could someone help me fix this ? 
 >   the syscall.h is pressent in ./usr/include/bits/syscall.h and not in
this
 > path. How can I go and change the path so that correct path is in place.
 > 
 > In file included from ./include/java-signal.h:17,
 >                  from
 >
/home/eplguser/Mudit/crosstool-0.42/build/powerpc-750-linux-gnu/gcc-4.1.0-gl
 > ibc-2.3.5/gcc-4.1.0/libjava/prims.cc:26:
 >
/opt/crosstool/gcc-4.1.0-glibc-2.3.5/powerpc-750-linux-gnu/powerpc-750-linux
 > -gnu/include/sys/syscall.h:32:27: error: bits/syscall.h: No such file or
 > directory
 >
/home/eplguser/Mudit/crosstool-0.42/build/powerpc-750-linux-gnu/gcc-4.1.0-gl
 > ibc-2.3.5/gcc-4.1.0/libjava/java/lang/Class.h: In member function
 > 'java::lang::Class* java::lang::Class::getComponentType()':
 >
/home/eplguser/Mudit/crosstool-0.42/build/powerpc-750-linux-gnu/gcc-4.1.0-gl
 > ibc-2.3.5/gcc-4.1.0/libjava/java/lang/Class.h:354: warning: dereferencing
 > type-punned pointer will break strict-aliasing rules
 >
/home/eplguser/Mudit/crosstool-0.42/build/powerpc-750-linux-gnu/gcc-4.1.0-gl
 > ibc-2.3.5/gcc-4.1.0/libjava/prims.cc: In function 'jint
 > _Jv_CreateJavaVM(JvVMInitArgs*)':
 >
/home/eplguser/Mudit/crosstool-0.42/build/powerpc-750-linux-gnu/gcc-4.1.0-gl
 > ibc-2.3.5/gcc-4.1.0/libjava/prims.cc:1274: error: 'SYS_sigaction' was not
 > declared in this scope
 > make[5]: *** [prims.lo] Error 1

/usr/include/bits/syscall.h is part of the target's operating system.
On my system it's in the glibc-headers package.  You need to take a
copy of the target's syscall.h and place it in the prefix along with
the other target headers.

Andrew.