J E Chimene

If anyone wants to run Cobol on VMS, they should apply for the Community License; whoch will provide VSI Cobol.

Since posting the prior note, I've learned about Sector7 and their port of gnucobol to Linux. Their modifications to gnucobol aren't available for review. I'm guessing they solved some interesting Cobol-specific portability issues; which issues I too would face. My work was always a hobbyist project. I don't think it's worth continuing after discovering this intersection of gnucobol & VMS. Thanks for your interest.

Since posting this note, I've learned about Sector7 and their port of gnucobol to Linux. Their modifications to gnucobol aren't available for review. I'm guessing they solved some interesting Cobol-specific portability issues; which issues I too would face. My work was always a hobbyist project. I don't think it's worth continuing after discovering this intersection of gnucobol & VMS. Thanks for your interest.

@sf-mensch I think there's still more to do to clean up the build environment for configure. The previous post is still relevant. Next tile I will post config.log Thanks!

Here's a result log based on the current configure Please ignore the errors creating/removing directories. They are benign; I'll address them, but not immediately. I'm intereested in any no results where you expect the name of the utility or yes My next step, unless I see a response that indicates other setup-style actions, is to take a look at config.sub $ bash ./configure rm: cannot remove 'conf8727': is a directory checking for a BSD-compatible install... build_aux/install-sh -c checking whether...

Here's an based on the current configure Please ignore the errors creating/removing directories. They are benign; I'll address them, but not immediately. I'm intereested in any no results where you expect the name of the utility or yes My next step, unless I see a response that indicates other setup-style actions, is to take a look at config.sub $ bash ./configure rm: cannot remove 'conf8727': is a directory checking for a BSD-compatible install... build_aux/install-sh -c checking whether build environment...

I was trying to spare you the issues. Some can be fixed by modifying the environment, the others are fixable by modifying the script. For gnuCobol: I have yet to sucesfully execute the configure script. The issues so far are very VMS-specific. 1) Referencing "/" from Bash yields a "Not Owner" error 2) Referencing the current default directory without a concealed logical name generates a "bad working directory" error 3) The configure script creates a working directory using a soft link, and somehow...

I was trying to spare you the issues. Some can be fixed by modifying the environment, the others are fixable by modifying the script. For gnuCobol: I have yet to sucesfully execute the configure script. The issues so far are very VMS-specific. 1) Referencing "/" from Bash yields a "Not Owner" error 2) Referencing the current default directory without a concealed logical name generates a "bad working directory" error 3) The configure script creates a working directory using a soft link, and somehow...