Re: [Bug-GnuCOBOL] [GnuCOBOL 3.0-rc1] testsuite: 18 19 20 failed

[Artie Arnoldt]

I think I found out what caused it.
I used my MinGW folder to build in but forgot to remove the previous build 
from  MinGW\sys
I did another build after deleting the old stuff  and everything worked OK.

Thanks

Artie

-----Original Message----- 
From: Simon Sobisch
Sent: Thursday, May 03, 2018 4:15 AM
To: address@hidden
Cc: address@hidden
Subject: Re: [Bug-GnuCOBOL] [GnuCOBOL 3.0-rc1] testsuite: 18 19 20 failed

Am 23.04.2018 um 23:17 schrieb Artie Arnoldt:
> I am testing out the new GnuCobol 3.0-rc1 release [...] running Window 10 
> 32-bit.
> I used my MinGW setup that I build OC R2.2 with.

Arnold Trembley has a similar environment and if I remember correctly
there were no unexpected failures.

> Attached are make screen log and make check screen log as well as the
> test suite log plus other files that were updated in tests folder.

Thank you. In 99,5% testsuite.log is the relevant file (was in your
case, too; it always includes atconfig and atlocal).

It shows an interesting reason for all the failed tests:

libcob: entry point 'prog' not found

This means libcob (internally started with cobcrun after compilation was
fine) found a prog.dll but this doesn't contain a "prog" entry point.

Can you please recheck that there is no prog.dll in the entries that are
included in the PATH entry in your MSYS environment? I *assume* you find
one. Please report back and we dig in further if needed or can think
about checking this beforehand - or rename the module and PROGRAM-ID
(which results in an entry point generation) for these three tests.

> I also ran make test here is the bottom of the screen log
>
> [...]
> Comparing total test results
> diff ./summary.txt summary.log
>
> make[3]: Leaving directory `/mingw/MSYS/gnucobol-3.0-rc1/tests/cobol85'

If you see this - which means there are no differences to the expected
result - then the tested NIST entries are all fine.
> Artie Arnoldt