bug-gnucobol
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[open-cobol-list] Re: [OpenCOBOL 0.23.30a] extension: 1-15 failed, data-


From: Keisuke Nishida
Subject: [open-cobol-list] Re: [OpenCOBOL 0.23.30a] extension: 1-15 failed, data-rep: 1-15 failed, cobol2002-run: 1 2 3 4 5 8 9 10 11 14 15 16 17 19 20 21 22 23 24 25 26 27 30 31 32 33 34 35 36 37 41 42 43 44 45 46 47 49 50 51 52 53 54 failed
Date: Wed Feb 11 16:15:55 2004
User-agent: Wanderlust/2.10.0 (Venus) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (Unebigoryƍmae) APEL/10.3 Emacs/21.2 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI)

Hi Frank,

Sorry for the late reply.

At Mon, 15 Dec 2003 11:21:28 +0100,
Polscheit, Frank wrote:
> 
> I've checked out the lastest version of module "open-cobol" from CVS and
> did the following instructions on CYGWIN (full installation based on
> Dec. 11):
> 
>   ./configure --with-db=4
>   make
>   make check
>   make install
> 
> I had to edit "libcob/fileio.c" by inserting "#define _WIN32" at the
> beginning of the file in order to hit the #ifndef in line 122 and 145,
> otherwise I got a compile error because of unknown/undefined LOCK_...
> etc.

I have modified the lines

  #ifndef _WIN32

to

  #if !(defined __CYGWIN__ || defined __MINGW32__)

so you can compile it.  I will rewrite the locking facility using
`fcntl' rather than `flock' for portability.

> Successfully compiled, the tests resulted in a lot of errors. The syntax
> check was the only successful one. Please find enclosed the log-files.
> When using the "/usr/local/bin/cobc.exe", it generates an executable,
> which always prompt an error window: "The application could not
> initialized properly (0xc0000005). Please klick OK to terminate."

I talked to a person who is working on the Cygwin port of open-cobol,
and he said this problem might be caused by the GMP library.  If you
use GMP 4.1.2 with the "gcd_ui.c.retval.diff" patch, which is included
in Cygwin, you will see the above error.  If you install GMP manually
without the patch above, you can avoid the error.

I am not sure why this error happens.  I personally do not use
Cygwin and cannot investigate it.  Please let me know if you find
a real solution to this problem.

Keisuke


reply via email to

[Prev in Thread] Current Thread [Next in Thread]