Everaldo Bernardo Cunha

Simon, I tried to generate the gnu cobol within of the FreeDOS. I got to install VBISAM and the shell script run ... but it always stop for doesn't find the file "config.h.in" ... Do you can help m

Okay, I did some tests with the GNU Cobol for FreeDOS. The first, I proceeded with the installation of the "VBISAM" in the ambient cross-compile and without to change the file "config.h", I executed the "cobc --info" command and the resulted is the log file "SEE-INFO.LOG". In the log file you can note the "VBISAM" is installed ... When I do the changes in the "config.h" and I proceed with the "make" and "make install", the resulted is other and to execute the command "cobc --info" it shows the "VBISAM"...

Simon, where are you? How you don't appear more, I decided to do more a test in FreeDOS ambient. You remember than I stood in the "not found Makefile.in.in" ... Ok! I passed of that part and I got resolved almost all ... now, the script "configure.status" stop in other file, it called, config.h.in ... really that file doesn't exist, because in the FreeDOS we have the case of the names with 8 characters the name and 3 characters of extension ... it exist how "CONFIG.H-I", so I renamed the entries...

Well, how you don't answer to my last post, I did more a experience ... I renamed the file ".../xml2/xmlreader.h" to ".../xml2/libxml2.h" and now I obtained a new messages from shell script "./configure" ... I send to you the resulted!

Simon, I noted the shell script has a fail: xml2. I put in the script just xml, so it doesn't execute the generation to the database. In the installer of the DJGPP there is the package "xml2104b.zip" and the same is installed! So, how configure shell script to it generates to database access with?

Sorry, I forgot to send the log file in relation to the "VBISAM" library ... it is in attachment !

More information: I compiled the file generated to the GNU Cobol with gcc and the result you can see in the screen-shot and log file attachments .... ....

I got configure the file "config.h" and I did a test with GNU Cobol, but it isn't creating the executable nor modules ... see the result in attachment logs files and batch file of compilation ....