Re: RFA: [PATCH]: MIPS enhancements to libgcj...

[David Daney <ddaney at avtrex dot com>]

Rainer Orth wrote:

> David Daney <ddaney@avtrex.com> writes:
>
>  
>
> > Index: gcc/doc/install.texi
> > ===================================================================
> > RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v
> > retrieving revision 1.230
> > diff -3 -u -p -r1.230 install.texi
> > --- gcc/doc/install.texi	20 Oct 2003 23:45:51 -0000	1.230
> > +++ gcc/doc/install.texi	21 Oct 2003 01:36:19 -0000
> > @@ -1112,6 +1112,17 @@ error message.
> > All support for systems which have been obsoleted in one release of GCC
> > is removed entirely in the next major release, unless someone steps
> > forward to maintain the port.
> > +
> > +@item --with-broken-dladdr
> > +Specify that libgcj should not try to use the dladdr function.  It does
> > +this to resolve stack trace addresses and on systems with a broken
> > +dladdr this can cause a SIGSEGV.
> > +
> > +@item --with-libgcj-mips-xgot
> > +Specify that libgcj should be built with -mxgot on MIPS systems.  The
> > +way in which libtool does multi-stage linking on systems with short
> > +maximum command line lengths can cause GOT overflow errors while
> > +linking.  This option enables a large GOT to work around the problem.
> > @end table
> >    
>
> This shouldn't be configure options in my opinion, but the problem should
> be detected by autoconf if at all possible.  Otherwise, just enable it in
> configure.{in, host} for the affected platforms.
>
> 	Rainer
>  
The only way I know of to detect the got overflow problem is to build 
libgcj and see what happens.  I don't think that can reasonably be done 
with autoconf (chicken and egg problem).

The only way to test for broken dladdr is likewise to build libgcj, 
install it on the target and run it.  Again something that cannot be 
done with autoconf

For cross builds it seems you have to tell configure what the target is 
capable of.

David Daney.