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

[Simon Sobisch]

Hi Paul,

while I was a little bit confused about the specs I've now understood it
as "Cygwin 32bit envrionment on Windows 64bit".

The tests failing are:

 NUM: FILE-NAME:LINE     TEST-GROUP-NAME
      KEYWORDS

  18: used_binaries.at:560 Run job after compilation
      runmisc job
  19: used_binaries.at:579 Run job after compilation (path specified)
      runmisc job
  20: used_binaries.at:599 Run job with optional arguments
      runmisc job

They test different variants of "cobc compiles the code and directly
starts the process afterwards".

All fail with
+libcob: entry point 'prog' not found

This is a place where we should extend the error handling to show more
details, but in general this always happens if the runtime:

* find the so/dll
* loads the so/dll
* cannot call the entry point that was generated

Interesting questions:
* Do you have any other cobc/cobcrun/libcob in PATH?
* Do you have any other prog.exe/prog.dll in PATH?

If we find out the exact reason that this happens we could patch
GnuCOBOL. A more detailed error handling may help, but I've only started
this without any actual test.

In general I'd advise to *not* use Cygwin32 on 64bit Windows but
Cygwin64 (if you want to use cygwin).

If you don't want to use Cygwin in general but only for GnuCOBOL I
highly recommend to use MinGW builds instead (a little bit harder to
build, but you can use the trusted binaries from Arnold Trembley if you
don't want to hack the GnuCOBOL source, or use his "how to create a
GnuCOBOL MinGW environment guide" to setup the MinGW environment and
build GnuCOBOL yourself).

Happy Hacking,
Simon

[1]: https://www.arnoldtrembley.com/GnuCOBOL.htm