Hello, I am a newcomer to using shells, open-source code, and cobol. I recently became interested in COBOL so I decided to get the latest version of GNUCobol(3.1.2) from the big green button for my 64-bit Windows 10 device. I already had MinGW installed, and ran up MinGW\msys\1.0\msys.bat from my cmd terminal. Then, using the opened shell I performed ./configure, but the terminal thre up something about BerkeleyDB, but luckily this thread here gave me the solution of just running "./configure --without-db", which started off well enough, until I then performed "make". I can't provide all of what the terminal gave out due to privacy conerns, but here's some important snippets that may be useful:
Frankly, I have no idea what is happening here so I would appreaciate any and all insight into this problem. If there is a past thread that could help me, please link it.
Thanks,
TriAttack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi TriAttack and welcome to the world of free software, shells, GnuCOBOL and COBOL.
There are more warnings than I'd expect on a "plain MSYS" environment, but when up-to-date that likely is a "match".
In general those warnings are just warnings, you can ignore those for now.
The lt-cobcrun.c thing is a hard error, and one I haven't seen before. I guess there are spaces and/or special characters in those path definitions, correct?
To ease the building you possibly want to run the process in a folder like "C:\Dev\GnuCOBOL" or similar, I guess that this will bring your build through and also allows to runmake check (and depending if you have perl installed also make test).
Building GnuCOBOL yourself is never wrong, but commonly only needed if you want to be sure to be able to adjust and inspect it at any time. While I still want to challenge you to go on (at least a bit) you may also go with getting the binaries; the official binary packages are found at https://www.arnoldtrembley.com/GnuCOBOL.htm and "nightly builds" with MinGW 32bit (and a bit outdated components) are also available, see https://sourceforge.net/projects/gnucobol/files/gnucobol/nightly_snapshots/.
Note: you may want to register/login, otherwise there's a manual moderation que to get posts shown - and it is always nice to be able to "recognize" people.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
... and nearly forgot: there is a good "Build Guide for MinGW GnuCOBOL" in both .pdf and .odt on Arnold's page, too.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-05-07
Thank you for the warm welcome! I honestly had no idea that I could just download the binary, but I think I'm going to give a manual build just one more try. You are spot on with one of the folder names-Window's "Program Files" directory has a space in it, which may have messed up the process. I'll return with my results.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-05-07
Alright, make worked but make check now says this:
ERROR: 1036 tests were run,
28 failed (22 expected failures).
50 tests were skipped.
Scrolling through the text, it seems that the following tests threw unexpected errors:
8,19,20,21,23,771
What should I do? Should I download a new version?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-05-07
Ok, I successfully extracted the binary and followed the ending steps of the pdf guide, but windows still does not recognize cobc as a command.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2022-05-07
Nevermind, it works now, just need to put a space before entering cobc. Thanks for all the help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, after some tinkering and messing with environment variables I finally have cobc up and running. Thanks again for all the help. Now I have to go get my hands dirty with COBOL!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I am a newcomer to using shells, open-source code, and cobol. I recently became interested in COBOL so I decided to get the latest version of GNUCobol(3.1.2) from the big green button for my 64-bit Windows 10 device. I already had MinGW installed, and ran up MinGW\msys\1.0\msys.bat from my cmd terminal. Then, using the opened shell I performed ./configure, but the terminal thre up something about BerkeleyDB, but luckily this thread here gave me the solution of just running "./configure --without-db", which started off well enough, until I then performed "make". I can't provide all of what the terminal gave out due to privacy conerns, but here's some important snippets that may be useful:
From earlier on:
Later:
This one repeated itself a lot, have no idea why the clashes repeated in the first place.
And finally:
Frankly, I have no idea what is happening here so I would appreaciate any and all insight into this problem. If there is a past thread that could help me, please link it.
Thanks,
TriAttack
Hi TriAttack and welcome to the world of free software, shells, GnuCOBOL and COBOL.
There are more warnings than I'd expect on a "plain MSYS" environment, but when up-to-date that likely is a "match".
In general those warnings are just warnings, you can ignore those for now.
The
lt-cobcrun.cthing is a hard error, and one I haven't seen before. I guess there are spaces and/or special characters in those path definitions, correct?To ease the building you possibly want to run the process in a folder like "C:\Dev\GnuCOBOL" or similar, I guess that this will bring your build through and also allows to run
make check(and depending if you have perl installed alsomake test).Building GnuCOBOL yourself is never wrong, but commonly only needed if you want to be sure to be able to adjust and inspect it at any time. While I still want to challenge you to go on (at least a bit) you may also go with getting the binaries; the official binary packages are found at https://www.arnoldtrembley.com/GnuCOBOL.htm and "nightly builds" with MinGW 32bit (and a bit outdated components) are also available, see https://sourceforge.net/projects/gnucobol/files/gnucobol/nightly_snapshots/.
Note: you may want to register/login, otherwise there's a manual moderation que to get posts shown - and it is always nice to be able to "recognize" people.
... and nearly forgot: there is a good "Build Guide for MinGW GnuCOBOL" in both .pdf and .odt on Arnold's page, too.
Thank you for the warm welcome! I honestly had no idea that I could just download the binary, but I think I'm going to give a manual build just one more try. You are spot on with one of the folder names-Window's "Program Files" directory has a space in it, which may have messed up the process. I'll return with my results.
Alright, make worked but make check now says this:
ERROR: 1036 tests were run,
28 failed (22 expected failures).
50 tests were skipped.
Scrolling through the text, it seems that the following tests threw unexpected errors:
8,19,20,21,23,771
What should I do? Should I download a new version?
Ok, I successfully extracted the binary and followed the ending steps of the pdf guide, but windows still does not recognize cobc as a command.
Nevermind, it works now, just need to put a space before entering cobc. Thanks for all the help!
Ok, after some tinkering and messing with environment variables I finally have cobc up and running. Thanks again for all the help. Now I have to go get my hands dirty with COBOL!