tiny-cobol-users

[Tiny-cobol-users] DB1x vs DB3x

[John R. C. <jo...@we...>]

I already use OpenCobol which works with DB 3. TinyCOBOL only
works with DB 1. Assuming these facts are correct, how do I
install tinyCOBOL without screwing up my existing OpenCobol
installation?

I want to test out TC because OpenCobol doesn't implement
positioning ACCEPT and DISPLAY statements and doesn't have a
SCREEN section. 
-- 
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf

Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf

Re: [Tiny-cobol-users] DB1x vs DB3x

[David E. <de...@us...>]

John R. Culleton wrote:

 > I already use OpenCobol which works with DB 3.
 > TinyCOBOL only works with DB 1. Assuming these
 > facts are correct, how do I install tinyCOBOL
 > without screwing up my existing OpenCobol
 > installation?

Actually TC will work with any version of DB (1.85.4 2.x 3.x 4.x),
however it only uses the DB 185 API.

Due to licensing issues it is recommended that a DB version prior to 2.x
be used.

Most uses do not have an issue with using DB version 2.x or above.

If you are using an RPM based system I would suggest using what ever
version of DB is available. As configuring TC to link with DB1 can be
very cumbersome.

There should be no conflicts in using both TC and OC on the same system.


 > I want to test out TC because OpenCobol doesn't implement
 > positioning ACCEPT and DISPLAY statements and doesn't have a
 > SCREEN section.

TC does support both ACCEPT/DISPLAY AT LINE/POS statement clauses, and
the screen section.

There are some examples enclosed with the source code, in the
'test.code' directories.

Re: [Tiny-cobol-users] DB1x vs DB3x

[John R. C. <jo...@we...>]

On Wednesday 03 August 2005 02:24 pm, David Essex wrote:
> John R. Culleton wrote:
>  > I already use OpenCobol which works with DB 3.
>  > TinyCOBOL only works with DB 1. Assuming these
>  > facts are correct, how do I install tinyCOBOL
>  > without screwing up my existing OpenCobol
>  > installation?
>
> Actually TC will work with any version of DB (1.85.4 2.x 3.x 4.x),
> however it only uses the DB 185 API.
>
> Due to licensing issues it is recommended that a DB version prior to 2.x
> be used.
>
> Most uses do not have an issue with using DB version 2.x or above.

OK, but the ./configure step blows up with the following message
---------------
Beginning DB library test link sequence
checking if db.h header belongs to version 1.x \(1.85-2\)... no
configure: error: header db.h for library db version 1.x \(1.85-2\) not 
found... aborting
----------------------
So how do I fake out the configure?
                                        
-- 
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf

Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf

Re: [Tiny-cobol-users] DB1x vs DB3x

[David E. <de...@us...>]

John R. Culleton wrote:

 > David Essex wrote:
 > ...
 >> Actually TC will work with any version of DB (1.85.4 2.x 3.x 4.x),
 >> however it only uses the DB 185 API.
 > ...
 > OK, but the ./configure step blows up with the following message
 >
 > Beginning DB library test link sequence
 > checking if db.h header belongs to version 1.x \(1.85-2\)... no
 > configure: error: header db.h for library db version 1.x \(1.85-2\)
 > not found... aborting
 >
 > So how do I fake out the configure?

That is a known problem usually found on RPM based systems.

The following configure option should fix the problem.

./configure --help
...
--with-libdb=[ARG] use DB library version (2 3 4)
...

Example:
./configure --with-libdb=db3

Re: [Tiny-cobol-users] DB1x vs DB3x

[John R. C. <jo...@we...>]

On Wednesday 03 August 2005 09:40 pm, David Essex wrote:
> John R. Culleton wrote:
>  > David Essex wrote:
>  > ...
>  >
>  >> Actually TC will work with any version of DB (1.85.4 2.x 3.x 4.x),
>  >> however it only uses the DB 185 API.
>  >
>  > ...
>  > OK, but the ./configure step blows up with the following message
>  >
>  > Beginning DB library test link sequence
>  > checking if db.h header belongs to version 1.x \(1.85-2\)... no
>  > configure: error: header db.h for library db version 1.x \(1.85-2\)
>  > not found... aborting
>  >
>  > So how do I fake out the configure?
>
> That is a known problem usually found on RPM based systems.
>
> The following configure option should fix the problem.
>
> ./configure --help
> ...
> --with-libdb=[ARG] use DB library version (2 3 4)
> ...
>
> Example:
> ./configure --with-libdb=db3

The working line is  a tad different:

 ./configure --with-libdb=3

But thanks for putting me on the right path.

BTW I run Slackware. NO RPMs here. 
-- 
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf

Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf

Re: [Tiny-cobol-users] DB1x vs DB3x

[David E. <de...@us...>]

John R. Culleton wrote:

 > David Essex wrote:
 >
 >> That is a known problem usually found on RPM based systems.
 > ...
 > BTW I run Slackware. NO RPMs here.

Well RPM based system is where the problem was first encountered, and
since has spread to other distributions.

The fundamental problem for the 'configure' script is how to determine
if DB1 is installed, and if so how to ensure that the TC run-time uses
only DB1.

On systems that have several versions of DB installed this is rather
difficult.