Our fortran tests were not very good. All the libraries created
commitf0cb3767cf800f7fc10f603f13640b01606614e1
authorPeter O'Gorman <peter@pogma.com>
Sun, 12 Sep 2004 13:36:17 +0000 (12 13:36 +0000)
committerPeter O'Gorman <peter@pogma.com>
Sun, 12 Sep 2004 13:36:17 +0000 (12 13:36 +0000)
treec7f471cdb5fc140b887e5f39f62635f916c40652
parent8240b4ebbac9a7608c489bd6a6128cb1609e7d40
Our fortran tests were not very good. All the libraries created
were convenience libs, so we did not test the creation of shared
libraries on any platform. Also none of the libs used any actual
fortran library calls, adding a call to write(*,*) in each lib
causes the tests to fail on darwin (and presumably other platforms).
These new tests would likely cause many more fortran test failures,
so if there is an error during make it is reported as SKIP.

* tests/f77demo-make.test: Don't fail hard, skip on failure.
* tests/f77demo/foof2.f: New file.
* tests/f77demo/foof3.f: New file.
* tests/f77demo/fprogram.f: Call routine in new lib.
* tests/f77demo/foof.f: Call routine in another new lib.
* tests/f77demo/Makefile.am: Make a couple of new libraries, add
$(FLIBS) to cprogram LDADD.
ChangeLog
tests/f77demo-make.test
tests/f77demo/Makefile.am
tests/f77demo/foof.f
tests/f77demo/foof2.f [copied from tests/f77demo/foof.f with 84% similarity]
tests/f77demo/foof3.f [copied from tests/f77demo/foof.f with 80% similarity]
tests/f77demo/fprogram.f