gnucobol-users
[Top][All Lists]
Advanced

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

Re: [open-cobol-list] parallel compilation


From: Boepple, Florian
Subject: Re: [open-cobol-list] parallel compilation
Date: Mon, 19 Sep 2016 08:05:14 +0000

Hi Erwan,

you can set the environment variable $TMPDIR.
If this is not set GnuCOBOL will look in $TMP and also $TEMP for a value.
If none of these are set "/tmp" will be used.

See function cob_gettmpdir() in libcob/common.c

Best regards
Florian



Von: Erwan Duroselle [mailto:address@hidden 
Gesendet: Montag, 19. September 2016 09:16
An: address@hidden
Betreff: [open-cobol-list] parallel compilation

Hi,

I'm a rather new to gnuCobol, so please forgive any obvious question.

I am trying to compile a rather large software (many thousands of programs), 
issued from AS400 and Microfocus, with gnuCobol 2.0 rc1, on a Centos VM.

Most of my programs compile wonderfully, though I may ask questions about the 
few remaining ones later.

My problem is when I try to compile several programs in parallel, to save 
compilation time.
Say A* programs runs in a shell, and B* in an other one, at the same time.
On about 5% of the programs, apparently randomly, I get errors like:

/tmp/cob6501_0.c:24:30: error: /tmp/cob6501_0.c.h : No such file or directory
/tmp/cob6501_0.c:47:34: error: /tmp/cob6501_0.c.l.h : No such file or directory
/tmp/cob6501_0.c: In function âBTRX030C_â:
/tmp/cob6501_0.c:59: error: âmoduleâ undeclared (first use in this function)
/tmp/cob6501_0.c:59: error: (Each undeclared identifier is reported only once
/tmp/cob6501_0.c:59: error: for each function it appears in.)
/tmp/cob6501_0.c:59: error: âcob_glob_ptrâ undeclared (first use in this 
function)
/tmp/cob6501_0.c:62: error: âcob_procedure_paramsâ undeclared (first use in 
this function)
/tmp/cob6501_0.c:65: error: âframe_ptrâ undeclared (first use in this function)
/tmp/cob6501_0.c:65: error: âframe_stackâ undeclared (first use in this 
function)

When compiled alone, those programs compile without any message.
When parallel compilation is launched again, simillar errors will happen on 
other programs, not on the same ones.
The same problem happens on an older 2.0 version from 2015, on an other RedHat 
box.

Does anyone have a clue on how to avoid these errors? 
I have tried to set up a temporary compilation directory, different from /tmp, 
but couldn't find a parameter for that.

Regards,
Erwan



reply via email to

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