User Activity

  • Posted a comment on ticket #99 on GnuCOBOL (formerly OpenCOBOL)

    I pulled down the 2.2 release candidate and compiled it with MS/VS 2017 (32-bit. VBVISAM was not available for 64-bit. At least, it wasn't included in the win_prerequisites_vc11.7z). It Worked! First time I've got an MS/VS build to work (I got mingw32 to build for the prior release candidate). Unfortunately, when I tested compiling my WSSORT program (same as above), it still gave me errors for the nested occurs depending on. Setting environment for GnuCOBOL. compile... -conf=c:\devtools\gnucobol\config\ibm.conf...

  • Posted a comment on ticket #99 on GnuCOBOL (formerly OpenCOBOL)

    I pulled the most recent release. Unless I'm doing it wrong (which is possible) it still isn't compiling nested ODOs. I realize this was pulled from the prior release candidate, but I was hoping it would make it into the final product, and somewhere I got the idea that it was in the works. Perhaps I'm just doing it wrong? I'm getting this error: WSSORT.cob: 133: error: reference to item containing nested ODO is not implemented This is my compile command: /cygdrive/e/DevTools/Cobol/gnu-cobol-2.0_rc-2_win/gnu-cobol-2.0/cobc/cobc.exe...

  • Posted a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    I apologize for the long delay in responding. Yes, I have tried Arnold's build guides. More than once. The build has always failed, for any of several reasons. I eventually ran out of time/patience for diagnosis and filling in the blanks. It mostly comes down to all the things you "just gotta know", that don't always make it into such guides. ...until yesterday, when the most recent source download successfully compiled with CygWin64. Now I am going to try to get the MingW version running, so I can...

  • Posted a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    Update: The error reported for the COPY/REPLACING was not a compiler error. It was my mistake. The copybooks in question had been "lost" at one time, and in the recreation, one of them was created with the contents of a second one. The tag between the ":" was thus incorrect. If there is a problem with the compiler, it is that it did not report that it couldn't find a match; it reported a character problem with the ":". Another person recently filed a related report, and when I went to make a reply...

  • Modified a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    I’m afraid I broke protocol and mentioned two bugs (and my personal frustration)....

  • Modified a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    I’m afraid I broke protocol and mentioned two bugs (and my personal frustration)....

  • Posted a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    I’m afraid I broke protocol and mentioned two bugs (and my personal frustration)....

  • Posted a comment on ticket #16 on GnuCOBOL (formerly OpenCOBOL)

    I work in Windows, and have never, in what is becoming a few years now, been able...

View All

Personal Data

Username:
williamlightner
Joined:
2010-01-27 07:44:41
Location:
Lowell / United States / CDT
Gender:
Male

Projects

  • No projects to display.

Skills

  • No skills entered.

Personal Tools