On Wed, Mar 01, 2006 at 02:11:21PM +0000, Andrew Haley wrote:
> H. J. Lu writes:
>  > On Wed, Mar 01, 2006 at 11:48:39AM +0000, Andrew Haley wrote:
>  > > Andrew Haley writes:
>  > >  > Andrew Pinski writes:
>  > >  >  > With clean sources on x86_64-linux-gnu, I am getting almost all 
> tests 
>  > >  >  > for running gij to fail.  Does anyone know what is going on here?
>  > >  > 
>  > >  > I'll have a try now.
>  > > 
>  > > You are right.  The error is
>  > > 
>  > > lt-gij: relocation error: 
> /home/aph/gcc/trunk/build-x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/libjava/.libs/libgcj.so.7:
>  symbol _Unwind_GetIPInfo, version GCC_4.2.0 not defined in file 
> libgcc_s.so.1 with link time reference
>  > > 
>  > > The problem is that gij has a hard-coded rpath to the install dir:
>  > > 
>  > > [EMAIL PROTECTED] libjava]$ readelf -d .libs/lt-gij 
>  > > 
>  > > Dynamic section at offset 0x830 contains 27 entries:
>  > >   Tag        Type                         Name/Value
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libgij.so.7]
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libgcj.so.7]
>  > >  0x0000000000000001 (NEEDED)             Shared library: 
> [libpthread.so.0]
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libgcc_s.so.1]
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]
>  > >  0x0000000000000001 (NEEDED)             Shared library: [libm.so.6]
>  > >  0x000000000000000f (RPATH)              Library rpath: 
> [/home/aph/gcc/trunk/build-x86_64-unknown-linux-gnu/x86_64-unknown-linux-gnu/libjava/.libs:/home/aph/gcc/install/lib/../lib64]
>  > > 
>  > > Running `make install' fixes it.  :-(
>  > > 
>  > 
>  > The fix was posted at
>  > 
>  > http://gcc.gnu.org/ml/gcc-patches/2004-09/msg01486.html
> 
> If it still works, please check it in.

Ooops. The correct patch is

http://gcc.gnu.org/ml/gcc-patches/2004-09/msg00663.html

for ltmain.sh. Libtool is braindead when libgcc_s is involved. Should
I check it in once it is verified?


H.J.

Reply via email to