Re: Problems Linking prims.o in libjava

David Daney <[email protected]>
Newsgroups gmane.comp.gcc.java.devel
Message-ID <[email protected]>
In the future please direct GCJ questions to [email protected]

Jackson Jones wrote:
> David,
> 
> My name is Jackson Jones. I work at a company called 2wire
> (www.2wire.com). We use Java (gcj) in a set-top-box (embedded,
> broadcom chipset, with a MIPS core).

Wow, I thought we were the only ones crazy enough to try something like 
that.


> I am building a new toolchain
> since our old one is based on 3.4.1 and we want to use NPTL threads
> instead of linuxthread.
> 
> I am getting a linking error when linking prims.o. It has to do with
> mips-signal.h file. The gcc version is 4.1.2, but I updated that file
> to the one in 4.2. That got rid of one linking error, but I am still
> getting the error (below). I was hoping you may have an idea what to
> do to get around the problem.
.
.
.
> /home/jjones/depot/mp/head/tools/gcc-4.1.2/libjava/prims.cc: In
> function 'void catch_segv(int, siginfo_t*, void*)':
> /home/jjones/depot/mp/head/tools/gcc-4.1.2/libjava/prims.cc:149:
> error: 'struct sigcontext' has no member named 'sc_pc'
> /home/jjones/depot/mp/head/tools/gcc-4.1.2/libjava/prims.cc: In
> function 'void catch_fpe(int, siginfo_t*, void*)':
> /home/jjones/depot/mp/head/tools/gcc-4.1.2/libjava/prims.cc:163:
> error: 'struct sigcontext' has no member named 'sc_pc'
> make[5]: *** [prims.lo] Error 1


For some reason you don't have the proper glibc header files installed 
in your sysroot.  sys/ucontext.h and bits.sigcontext.h are likely incorrect.


> 
> Here are the options I am using to configure glibc and gcc with in
> case they are relevant.
> 

I would recommend the instructions found here:

http://cross-lfs.org/view/svn/mips/

for bootstrapping a cross-compiler.  For gcj/libgcj I would recommend 
binutils 2.18 or later and the latest GCC 4.2.x or 4.3.x.  I have been 
using glibc 2.6.1 and 2.7

David Daney
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.