This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/31928] Libjava testsuite not setting test environment parameters correctly.
- From: "davek at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 25 Mar 2010 14:37:54 -0000
- Subject: [Bug testsuite/31928] Libjava testsuite not setting test environment parameters correctly.
- References: <bug-31928-13830@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #2 from davek at gcc dot gnu dot org 2010-03-25 14:37 -------
(In reply to comment #0)
> The manner is which Java is being checked _seems_ completely different. I'm not
> a Java expert, in fact I only know a little about it - shouldn't Java be
> (identical) _independant_ of the platform ?
This is kind-of a false inference; GCJ compiles java to native code, so most of
the tests would be expected to build somewhat differently on different
platforms, according to how libtool configures itself for the platform's
features. However, it did lead you to spot a real problem. Running the tests
these days, set_ld_library_path_env_vars is called correctly, so this has been
fixed at some stage.
Backporting it to 4.2 is left as an exercise, sorry! :-O
--
davek at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |FIXED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31928