gcj/196: gcj compiled class will not run because of shared lib error!

[Bryce McKinlay]

The following reply was made to PR gcj/196; it has been noted by GNATS.

From: Bryce McKinlay <bryce@albatross.co.nz>
To: java-gnats@sourceware.cygnus.com
Cc:  
Subject: Re: gcj/196: gcj compiled class will not run because of shared lib 
 error!
Date: Mon, 10 Apr 2000 23:40:26 +1200

 Tom Tromey wrote:
 
 >  Mo> Is this one of those issues that will magically go away when
 >  Mo> libgcj becomes part of the main gcc toolchain?
 >
 >  No.  It does go away once libgcj is installed as part of the overall
 >  system though.
 >
 >  The last discussion on this was last month or so.  I should look up
 >  the answer, but I'm feeling lazy now.
 
 I searched through the list archives but couldn't find a reason why
 --rpath shouldn't
 be used, only more discussion along the lines of "hmm, isn't there a
 reason that we
 dont use rpath?"
 
 As long as LD_LIBRARY_PATH overrides the rpath setting, I think we
 should use it. If
 it turns out there is a problem with it then we can allways reverse the
 change.
 
 regards
 
   [ bryce ]