This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug java/11865] New: libjava testsuite fails to find libgcc.so


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11865

           Summary: libjava testsuite fails to find libgcc.so
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: davem at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: sparc-unknown-linux-gnu
  GCC host triplet: sparc-unknown-linux-gnu
GCC target triplet: sparc-unknown-linux-gnu

If you don't have gcc-3.3.x installed already, the libjava
testsuite executable tests will fail because it does not
end up finding the libgcc.so in the build tree when executing
the libjava test executables.

It ends up using the one installed on your system already.

So, for example, if you had gcc-3.2.x installed the libjava
testsuite executables would all crash due to being unable
to find the GCC_3.3 version in the various symbols used in
libgcc.so

Probably some problem with setting LD_LIBRARY_PATH.
The libjava testsuite does not output the complete command
line it uses to invoke the executables it runs into libjava.log,
if it did it might be easier to diagnose this problem.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]