[Bug fortran/38946] [trunk regression] gcc trunk 143562 - Testsuite - gfortran failing tests that worked previously

["mikael at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>]

------- Comment #4 from mikael at gcc dot gnu dot org  2009-01-26 18:42 -------
(In reply to comment #3)
> This is not so much an error in Fortran than it is an error in the
> scripting and it's ability to add it's own LD_LIBRARY_PATH components.
No. The current linking scheme links to the just-built libgfortran, not to the
system libgfortran. This is fine, because it is the newly built library that we
want to test. 

> They worked last week.
Sure, this is a regression. 

> Here is my most recent test. Above you ask "Could you try before/after this"
> do you mean compile and run the Testuite on bothboth "r143461" and "r143463"?
Yes. But to save time you can update only fortran or libgfortran and narrow the
testsuite run to the failing tests using the RUNTESTFLAGS variable as explained
here http://gcc.gnu.org/wiki/TestCaseWriting
Furthermore, as your tests show that the failure is in the libgfortran, there
is only one commit in that area in the window you gave (r143454-r143562): 

------------------------------------------------------------------------
r143541 | domob | 2009-01-21 14:34:55 +0100 (mer. 21 janv. 2009) | 29 lines

I don't know though how this could cause system-dependent failures :-(. Daniel?

> Thanks for fixing this,
Thanks for helping to fix this. 


-- 

mikael at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|gcc trunk 143562 - Testsuite|[trunk regression]?gcc trunk
                   |- gfortran failing tests    |143562 - Testsuite -
                   |that worked previously      |gfortran failing tests that
                   |                            |worked previously


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