Re: [open-cobol-list] gcc compile error with CBL_OPEN_FILE

[schlehuberc]

Thanks Sergey,

Setting the sticky-linkage to no worked.

I am now faced with mutually exclusive
items.

I need to use assign-clause=ibm which
is set in the ibm.conf, and sticky-linkage=no, which is set in the mf.conf.

If possible, I would like to avoid having
to create a new .conf file in the local/share directory (one more thing
to missing on migrations).

Two thoughts:

1)
Is it possible to be able to override
conf settings via the command line when executing cobc?

2)
I tried to create a new .conf file in
a directory that is different from the local/share/...
The COB_CONFIG_DIR
only accepts a single directory path.
Could this be set up to accept multiple
directories, and be : delimited?
This way the new .conf file could be
included as part of the application.


"Sergey Kashyrin" <address@hidden>
wrote on 06/20/2007 10:57:19 AM:

> Hi,
> 
> Set 
> sticky-linkage: no
> 
> I don't think you need it
> I'm usually also setting
> #undef COB_PARAM_CHECK
> 
> in config.h
> to avoid issues when calling Cobol from C/C++ etc.
> 
> Regards,
> Sergey
> 
> ----- Original Message ----- 
> From: address@hidden 
> To: address@hidden 
> Sent: Wednesday, June 20, 2007 9:57 AM
> Subject: [open-cobol-list] gcc compile error with CBL_OPEN_FILE
> 
> 
> SAMPFLE.c:380: error: too many arguments to function `CBL_OPEN_FILE'
> SAMPFLE.c:480: error: too many arguments to function `CBL_READ_FILE'
> SAMPFLE.c:872: error: too many arguments to function `CBL_READ_FILE'
> SAMPFLE.c:1033: error: too many arguments to function `CBL_CLOSE_FILE'
>