tiny-cobol-users

Re: [Tiny-cobol-users] Extra stuff in assembler

[Chris <cbo...@mi...>]

OK, that solved part of the problem.  Thanks, I didn't know the proper
gcc options to use.  I still get this error though:
as -o BuildWAtkTab.o BuildWAtkTab.s
BuildWAtkTab.s: Assembler messages:
BuildWAtkTab.s:35: Error: suffix or operands invalid for `mov'
BuildWAtkTab.s:44: Error: suffix or operands invalid for `mov'

Paradoxically, when I remove those #sec:0 references to eliminate the
above error, the gcc step still chokes:
gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lhtcobol2 -lm -ldb -ldl
BuildWAtkTab.o: In function `main':
BuildWAtkTab.o(.text+0x4c): undefined reference to `ww_base0'
BuildWAtkTab.o(.text+0x68): undefined reference to `ww_base0'
collect2: ld returned 1 exit status

On Thu, 2002-08-29 at 17:46, Rildo Pragana wrote:

    Hi Chris,
   =20
    On 29 Aug 2002, Chris Borgn=E6s wrote:
   =20
    > It's been years and years since I really looked at assembler, but I
    > found an oddity.  I try to build my program and I get the following
    > error:
    > BuildWAtkTab.s: Assembler messages:
    > BuildWAtkTab.s:35: Error: suffix or operands invalid for `mov'
    > BuildWAtkTab.s:44: Error: suffix or operands invalid for `mov'
    >
    > I do a htcobol -S and look at the result and this is what I see:
    >
    > .Linite_main:
    >  leal	main, %eax
    > 	pushl	%eax
    > 	leal	.Lend_pgm_main, %eax
    > 	pushl	%eax
    > 	pushl	$3
    > 	movl	$ww_base0+4 #sec:0, %eax
    > 	pushl	%eax
    > 	movl	$w_base0+4, %eax
    > 	pushl	%eax
    > 	movl	$s_base0+4, %eax
    > 	pushl	%eax
    > 	call	cob_open
    > 	addl	$16, %esp
    > 	pushl	$3
    > 	movl	$ww_base0+38 #sec:0, %eax
    > 	pushl	%eax
    > 	movl	$w_base0+20, %eax
    > 	pushl	%eax
    > 	movl	$s_base0+38, %eax
    > 	pushl	%eax
    > 	call	cob_open
    >
    > The as command seems to work fine once I remove the #sec:0 entries, b=
ut
    > gcc fails:
    > gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lm
    > BuildWAtkTab.o: In function `main':
    > BuildWAtkTab.o(.text+0x4c): undefined reference to `ww_base0'
    > BuildWAtkTab.o(.text+0x68): undefined reference to `ww_base0'
    > /usr/local/lib/libhtcobol.a(fileio.o): In function `cob_open':
    > fileio.o(.text+0x563): undefined reference to `__db185_open'
    > fileio.o(.text+0x5d6): undefined reference to `__db185_open'
    > /usr/local/lib/libhtcobol.a(fileio.o): In function `sort_open':
    > fileio.o(.text+0x385f): undefined reference to `__db185_open'
    > collect2: ld returned 1 exit status
    >
    > What's wrong?
    >
   =20
    Well, from the errors shown by gcc, it seems you missed to include
    -ldb to link with libdb. It is needed if your program uses any kind
    of file access, even if no indexes are in use.
   =20
    best regards,
    Rildo
     ------------------------------------------------------------------
     Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
     R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
     Recife, PE - Brazil 52011-000   +55-81-3223-5694
   =20
   =20
   =20
    -------------------------------------------------------
    This sf.net email is sponsored by:ThinkGeek
    Welcome to geek heaven.
    http://thinkgeek.com/sf
    _______________________________________________
    Tin...@li...

https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users

   =20

Re: [Tiny-cobol-users] Extra stuff in assembler

[Rildo P. <ri...@pr...>]

Hi Chris,

On 29 Aug 2002, Chris Borgn=E6s wrote:

> It's been years and years since I really looked at assembler, but I
> found an oddity.  I try to build my program and I get the following
> error:
> BuildWAtkTab.s: Assembler messages:
> BuildWAtkTab.s:35: Error: suffix or operands invalid for `mov'
> BuildWAtkTab.s:44: Error: suffix or operands invalid for `mov'
>
> I do a htcobol -S and look at the result and this is what I see:
>
> .Linite_main:
>  leal=09main, %eax
> =09pushl=09%eax
> =09leal=09.Lend_pgm_main, %eax
> =09pushl=09%eax
> =09pushl=09$3
> =09movl=09$ww_base0+4 #sec:0, %eax
> =09pushl=09%eax
> =09movl=09$w_base0+4, %eax
> =09pushl=09%eax
> =09movl=09$s_base0+4, %eax
> =09pushl=09%eax
> =09call=09cob_open
> =09addl=09$16, %esp
> =09pushl=09$3
> =09movl=09$ww_base0+38 #sec:0, %eax
> =09pushl=09%eax
> =09movl=09$w_base0+20, %eax
> =09pushl=09%eax
> =09movl=09$s_base0+38, %eax
> =09pushl=09%eax
> =09call=09cob_open
>
> The as command seems to work fine once I remove the #sec:0 entries, but
> gcc fails:
> gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lm
> BuildWAtkTab.o: In function `main':
> BuildWAtkTab.o(.text+0x4c): undefined reference to `ww_base0'
> BuildWAtkTab.o(.text+0x68): undefined reference to `ww_base0'
> /usr/local/lib/libhtcobol.a(fileio.o): In function `cob_open':
> fileio.o(.text+0x563): undefined reference to `__db185_open'
> fileio.o(.text+0x5d6): undefined reference to `__db185_open'
> /usr/local/lib/libhtcobol.a(fileio.o): In function `sort_open':
> fileio.o(.text+0x385f): undefined reference to `__db185_open'
> collect2: ld returned 1 exit status
>
> What's wrong?
>

Well, from the errors shown by gcc, it seems you missed to include
-ldb to link with libdb. It is needed if your program uses any kind
of file access, even if no indexes are in use.

best regards,
Rildo
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694

Re: [Tiny-cobol-users] Name of index file.

[Hudson R. <hud...@so...>]

Hi win,

> Just adding ".idx" looks ok. 

I think too. For now, is to wait the developers opinion..

Regards!
Hudson

Re: [Tiny-cobol-users] Extra stuff in assembler

[Hudson R. <hud...@so...>]

Hi Chris,

> The as command seems to work fine once I remove the #sec:0 entries, but
> gcc fails:
> gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lm
> BuildWAtkTab.o: In function `main':
> BuildWAtkTab.o(.text+0x4c): undefined reference to `ww_base0'
> BuildWAtkTab.o(.text+0x68): undefined reference to `ww_base0'
> /usr/local/lib/libhtcobol.a(fileio.o): In function `cob_open':
> fileio.o(.text+0x563): undefined reference to `__db185_open'
> fileio.o(.text+0x5d6): undefined reference to `__db185_open'
> /usr/local/lib/libhtcobol.a(fileio.o): In function `sort_open':
> fileio.o(.text+0x385f): undefined reference to `__db185_open'
> collect2: ld returned 1 exit status
> 
> What's wrong?

add the libraries -ldb, -ldl and -lhtcobol2 in link step. 
ex:

gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lhtcobol2 -lm -ldb -ldl

Hope this helps.

Hudson

[Tiny-cobol-users] Extra stuff in assembler

[Chris <cbo...@mi...>]

It's been years and years since I really looked at assembler, but I
found an oddity.  I try to build my program and I get the following
error:
BuildWAtkTab.s: Assembler messages:
BuildWAtkTab.s:35: Error: suffix or operands invalid for `mov'
BuildWAtkTab.s:44: Error: suffix or operands invalid for `mov'

I do a htcobol -S and look at the result and this is what I see:

.Linite_main:
 leal	main, %eax
	pushl	%eax
	leal	.Lend_pgm_main, %eax
	pushl	%eax
	pushl	$3
	movl	$ww_base0+4 #sec:0, %eax
	pushl	%eax
	movl	$w_base0+4, %eax
	pushl	%eax
	movl	$s_base0+4, %eax
	pushl	%eax
	call	cob_open
	addl	$16, %esp
	pushl	$3
	movl	$ww_base0+38 #sec:0, %eax
	pushl	%eax
	movl	$w_base0+20, %eax
	pushl	%eax
	movl	$s_base0+38, %eax
	pushl	%eax
	call	cob_open

The as command seems to work fine once I remove the #sec:0 entries, but
gcc fails:
gcc -o BuildWAtkTab BuildWAtkTab.o -lhtcobol -lm
BuildWAtkTab.o: In function `main':
BuildWAtkTab.o(.text+0x4c): undefined reference to `ww_base0'
BuildWAtkTab.o(.text+0x68): undefined reference to `ww_base0'
/usr/local/lib/libhtcobol.a(fileio.o): In function `cob_open':
fileio.o(.text+0x563): undefined reference to `__db185_open'
fileio.o(.text+0x5d6): undefined reference to `__db185_open'
/usr/local/lib/libhtcobol.a(fileio.o): In function `sort_open':
fileio.o(.text+0x385f): undefined reference to `__db185_open'
collect2: ld returned 1 exit status

What's wrong?

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

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

At 10:38 AM 29/08/02 -0300, Rildo Pragana wrote:

> Here is the typescript of my session. (please see at the end)
> ...
> On Thu, 29 Aug 2002, David Essex wrote:
>
>> What kind of problems are you having ?
>
>Script started on Thu Aug 29 13:32:41 2002
>#./configure
>creating cache ./config.cache
> ...
>Beginning DB library header search sequence
>checking for db_185.h... no
>checking for db.h... yes
>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

From the lack of the db_185.h file, I think you have DB version 4 installed
on your system.

At 10:44 AM 29/08/02 -0300, Hudson Reis wrote:
>
>./configure --with-libdb=4 (To version 4 of libdb)

Have you tries the above configure option ?

Note that you should remove the configure cache file './config.cache', as
it can cause problems.


> Of course, I could create some headers and place libraries in convenient
> locations, so the configure script will like that, but suppose I'm a simple
> TC user, not a developer.

Different distributions have multiple DB versions, consequently there is no
way that I know of, to cleanly resolve this problem.




David Essex

[Tiny-cobol-users] OK, I'm able to compile.

[Rildo P. <ri...@pr...>]

Hi all,

Thanks for all the feedback and help I received from all of you.
I'm able to compile now, but with the following command line:

./configure --with-libdb=3

(I must not forget that again!i :^)

Though it don't work well for "--with-libdb=2",
I don't know exactly why!
Well, I'm not going to spend time on that stuff. Let me do
something more useful.

best regards,
Rildo
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

[Andrew C. <apc...@so...>]

Hi Rildo,

I have no problem with the Idea.
Just remember however that there are different versions we will need to
include depending on weather you are compiling for Linux or Cygwin or
Mingw32.

Regards
Andrew Cameron

----- Original Message -----
From: "Rildo Pragana" <ri...@pr...>
To: <tin...@li...>
Sent: 29 August 2002 06:50
Subject: [Tiny-cobol-users] Problems compiling with libdb, again.


> Hi all,
>
> I found that trying to compile TC have some problems, at least
> in my Slackware 8.0. Before patching it too much, I would ask
> you (the other developers) what do you think if we include
> db-1.85 source in our source tree, so the troubles with
> configuration go away forever?
>
> I choose version 1.85 because it is the only free version of this
> library, and anyway we don't support the added features of the
> other more recent releases of libdb.
> This way, our configuration scripts become much more easy to maintain
> and there will be no issues related to libdb anymore.
>
> What do you think?
>
> best regards,
> Rildo
>  ------------------------------------------------------------------
>  Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
>  R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
>  Recife, PE - Brazil 52011-000   +55-81-3223-5694
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Tin...@li...
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users

Re: [Tiny-cobol-users] Runtime libraries unified and compiled as shared objects.

[Hudson R. <hud...@so...>]

Hi Ferran,

> We can still create the libraries as a static objects for debug > purposes.

In a shared library is not possible debug the program?

> This is a big change, so try to compìle your old programs and report 
> problems to this list.

When I compile any program, the compiler shows the following warning:

I modify my htcobolrc file and warnings not shows more. 

I don't have access to cvs servers, then, could you add the htcobolrc file, commenting the LT_HT2_LIBS variable?

Thanks.
Hudson

-- 
Hudson Reis                                       hud...@so...


-- 
Hudson Reis                                       hud...@so...

[Tiny-cobol-users] Compilation error in test.code/tdb03

[Hudson R. <hud...@so...>]

Hi all,

In test.code/tdb03/tdb03.cob, in compilation, shows the following error:

tdb03.cob:    73: bad formed display statement

This error occurs for this:

in line 71, the DISPLAY verb have been used incorrectly, see:

 PROCEDURE DIVISION.
	display "Content-type: text/html"
	display 

The correct way is: 

 PROCEDURE DIVISION.
	display "Content-type: text/html"
	display x"00" 

I don't have access to cvs servers then, developers, could you fix the little fault in this program? 

Thanks.
Hudson

-- 
Hudson Reis                                       hud...@so...

Re: [Tiny-cobol-users] Runtime libraries unified and compiled as shared objects.

[Hudson R. <hud...@so...>]

Hi Ferran,

> We can still create the libraries as a static objects for debug > purposes.

In a shared library is not possible debug the program?

> This is a big change, so try to compìle your old programs and report 
> problems to this list.

When I compile any program, the compiler shows the following warning:

I modify my htcobolrc file and warnings not shows more. 

I don't have access to cvs servers, then, could you add the htcobolrc file, commenting the LT_HT2_LIBS variable?

Thanks.
Hudson

-- 
Hudson Reis                                       hud...@so...

Re: [Tiny-cobol-users] Runtime libraries unified and compiled as shared objects.

[Hudson R. <hud...@so...>]

Hi Ferran,

> We can still create the libraries as a static objects for debug > purposes.

In a shared library is not possible debug the program?

> This is a big change, so try to compìle your old programs and report 
> problems to this list.

When I compile any program, the compiler shows the following warning:

I modify my htcobolrc file and warnings not shows more. 

I don't have access to cvs servers, then, could you add the htcobolrc file, commenting the LT_HT2_LIBS variable?

Thanks.
Hudson

[Tiny-cobol-users] Compilation error in test.code/tdb03

[Hudson R. <hud...@so...>]

Hi all,

In test.code/tdb03/tdb03.cob, in compilation, shows the following error:

tdb03.cob:    73: bad formed display statement

This error occurs for this:

in line 71, the DISPLAY verb have been used incorrectly, see:

 PROCEDURE DIVISION.
	display "Content-type: text/html"
	display 

The correct way is: 

 PROCEDURE DIVISION.
	display "Content-type: text/html"
	display x"00" 

I don't have access to cvs servers then, developers, could you fix the little fault in this program? 

Thanks.
Hudson

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

[Hudson R. <hud...@so...>]

Hi Rildo,

> I found that trying to compile TC have some problems, at least
> in my Slackware 8.0. Before patching it too much, I would ask
> you (the other developers) what do you think if we include
> db-1.85 source in our source tree, so the troubles with
> configuration go away forever?

In my point of view, include db-1.85 sources in source tree isn't a good idea so the libdb sources have a 272,892kb. The most dammaged is the dial-up concection user, like me and others. :(

For example: SourceNavigator(1), have a 15MB(in sources!), however, is included in your source tree the sources of libdb, grep, itcl, tcl8.1, tk8.1 and tix. If I remove this packages and compact again, the size of source navigator's package is 7MB. Again, the most dammaged is the dial-up connection user. :(
 
> I choose version 1.85 because it is the only free version of this
> library, and anyway we don't support the added features of the
> other more recent releases of libdb.
> This way, our configuration scripts become much more easy to maintain
> and there will be no issues related to libdb anymore.
> 
> What do you think?

I don't think a good idea, so the user couldn't configure the libdb version. The current way is very good for me:

./configure --with-libdb=2 (To version 2 of libdb)
./configure --with-libdb=3 (To version 3 of libdb)
./configure --with-libdb=4 (To version 4 of libdb)
 
Regards,
Hudson

1) SourceNavigator.
   http://sources.redhat.com/sourcenav

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

[Rildo P. <ri...@pr...>]

Hi David,

Here is the typescript of my session. (please see at the end)
Of course, I could create some headers and place libraries in convenient
locations, so the configure script will like that, but suppose I'm a simple
TC user, not a developer.

On Thu, 29 Aug 2002, David Essex wrote:

> What kind of problems are you having ?
>
> I am using  Slackware 7, which includes DB version 2.4.14, and I can
> configure and build, the CVS version I downloaded yesterday, with out
> any problems.


Script started on Thu Aug 29 13:32:41 2002
root@roteador:/tmp/development# ./configure
creating cache ./config.cache
checking for gcc... gcc
checking for as... as
checking for a BSD compatible install... /usr/bin/ginstall -c
checking whether ln -s works... yes
checking whether make sets ${MAKE}... yes
checking for ranlib... ranlib
checking for ar... ar
checking for flex... flex
checking for bison... bison
checking for expand... /usr/bin/expand
checking how to run the C preprocessor... gcc -E
checking whether cross-compiling... no
checking for ANSI C header files... yes
checking for stdio.h... yes
checking for alloca.h... yes
checking for errno.h... yes
checking for fcntl.h... yes
checking for limits.h... yes
checking for sys/time.h... yes
checking for unistd.h... yes
checking for malloc.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for strings.h... yes
checking for utime.h... yes
checking for ctype.h... yes
checking for sys/stat.h... yes
checking for sys/types.h... yes
checking for getopt.h... yes
checking for ltdl.h... yes
checking for working const... yes
checking for off_t... yes
checking for size_t... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for 8-bit clean memcmp... yes
checking for vprintf... yes
checking for strcspn... yes
checking for strdup... yes
checking for strerror... yes
checking for strspn... yes
checking for -lm... yes
Beginning DB library header search sequence
checking for db_185.h... no
checking for db.h... yes
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
root@roteador:/tmp/development# exit

Script done on Thu Aug 29 13:33:00 2002
---------------------------------------------------------------------------

best regards,
Rildo
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

[Chris <cbo...@mi...>]

I too have these problems, but with RH7.3.  Having source from another
project might solve our current troubles, but might cause others.  Two
of the same installed versions of libdb on one machine could be quite
messy.  Not that I have a better suggestion; that just seems very
inelegant.

On Thu, 2002-08-29 at 05:50, Rildo Pragana wrote:

    Hi all,
    
    I found that trying to compile TC have some problems, at least
    in my Slackware 8.0. Before patching it too much, I would ask
    you (the other developers) what do you think if we include
    db-1.85 source in our source tree, so the troubles with
    configuration go away forever?
    
    I choose version 1.85 because it is the only free version of this
    library, and anyway we don't support the added features of the
    other more recent releases of libdb.
    This way, our configuration scripts become much more easy to maintain
    and there will be no issues related to libdb anymore.
    
    What do you think?
    
    best regards,
    Rildo
     ------------------------------------------------------------------
     Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
     R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
     Recife, PE - Brazil 52011-000   +55-81-3223-5694
    
    
    
    -------------------------------------------------------
    This sf.net email is sponsored by:ThinkGeek
    Welcome to geek heaven.
    http://thinkgeek.com/sf
    _______________________________________________
    Tin...@li...

https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users

    

Re: [Tiny-cobol-users] Problems compiling with libdb, again.

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

  Rildo Pragana wrote:

>I found that trying to compile TC have some problems, at least
>in my Slackware 8.0. Before patching it too much, I would ask
>you (the other developers) what do you think if we include
>db-1.85 source in our source tree, so the troubles with
>configuration go away forever?
>
What kind of problems are you having ?

I am using  Slackware 7, which includes DB version 2.4.14, and I can 
configure and build, the CVS version I downloaded yesterday, with out 
any problems.

>I choose version 1.85 because it is the only free version of this
>library, and anyway we don't support the added features of the
>other more recent releases of libdb.
>This way, our configuration scripts become much more easy to maintain
>and there will be no issues related to libdb anymore.
>
>What do you think?
>
>  
>
This may create more problems that it will solve, as many ditributions 
have more than one version of DB installed.


David Essex

[Tiny-cobol-users] Problems compiling with libdb, again.

[Rildo P. <ri...@pr...>]

Hi all,

I found that trying to compile TC have some problems, at least
in my Slackware 8.0. Before patching it too much, I would ask
you (the other developers) what do you think if we include
db-1.85 source in our source tree, so the troubles with
configuration go away forever?

I choose version 1.85 because it is the only free version of this
library, and anyway we don't support the added features of the
other more recent releases of libdb.
This way, our configuration scripts become much more easy to maintain
and there will be no issues related to libdb anymore.

What do you think?

best regards,
Rildo
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694

[Tiny-cobol-users] Bernard Giroud, please.

[Rildo P. <ri...@pr...>]

Hi Bernard,

I was unable to send mail to your aol.com account, sorry. So, here is the
original message I'd like to send you.

-------------------------------------------------------------------------
Bon jour :)

With the resign of David Essex as our "all hands man", we need another
mailing list moderator.
I have taken the liberty of including your name (and this e-mail address
at aol.com) as our maintainer, as well as Hudson Reis (another
brazilian like me).

There is not much to do about that, as most administrative issues I can
solve myself, but just in case something go wrong with me, or I'm unable
to answer the requests in time...
Please tell me if you accept this job.

best regards,
Rildo
 ------------------------------------------------------------------
 Rildo Pragana                   FPGA/uControllers * Linux * tcl/tk
 R.Joaquim Nabuco,92/302 Derby   http://www.pragana.net
 Recife, PE - Brazil 52011-000   +55-81-3223-5694

Re: [Tiny-cobol-users] WEB page maintainer required

[<bur...@ya...>]

I would be interested in helping out, please let me
know what I can do to assist.

Regards

Peter

 --- David Essex <de...@ar...> wrote: > TC
requires a WEB page maintainer. 
> 
> Any volunteer please submit his or her request to
> the TC mailing list.
> 
> 
> 
> 
> 
> David Essex
> 
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by: OSDN - Tired of
> that same old
> cell phone?  Get a new here for FREE!
>
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
> _______________________________________________
> Tin...@li...
>
https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users 

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

[Tiny-cobol-users] WEB page maintainer required

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

TC requires a WEB page maintainer. 

Any volunteer please submit his or her request to the TC mailing list.





David Essex

[Tiny-cobol-users] Off topic

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

Effective August 28 2002, GMT, I will no longer participate in any further
development of TC.



David Essex

[Tiny-cobol-users] Runtime libraries unified and compiled as shared objects.

[Ferran P. <fer...@re...>]

I have uploaded serious changes to CVS.

Now the runtime system is only one library  that includes all the 
features. This library is created as a shared object and is linked with 
all the used libraries, so now the programs created only need to be 
linked to libhtcobol (-lhtcobol) and don't need to be linked to curses, 
db etc...

The runtime created as a shared object make all the compiled cobol 
programs smaller, and reduces the problems found on executing string and 
other operations on routines.

In general this should reduce the complexity of compilation and linking 
 and  now we can eliminate the code that calculates the libraries to 
link on the compiler, and make it simpler.

We can still create the libraries as a static objects for debug purposes.

This is a big change, so try to compìle your old programs and report 
problems to this list.

-- 
Salutacions / Regards
+---------------------------------------------------------------+
| Ferran Pegueroles Forcadell                                   |
| mailto:fer...@re...                          |
| Tels (+34)937252106 - (+34)667658535                          |
| C/Unió 44 2n 2a 08201 Sabadell (BCN)                          |
+---------------------------------------------------------------+

Re: [Tiny-cobol-users] problems with string in dynamic libraries

[Ferran P. <fer...@re...>]

All this problems seem cause because the runtime librari is not linked 
with the routine, only is linked with the main program, andf the main 
program only is linked with the modules he needs, if it doesn't use the 
string is not linked with the string module (inside the libhtcobol.a).

I think that a lot of problems of this kind can be resolvend if we 
generate the runtime as a shared object (only one file). and linke this 
shared object with the main programs and the routines.

Another good thing about this is that we won't need to link all the 
executables or modules with curses libdb or libltdl. We only link this 
with the runtime and the porogrames only need to be linked with the runtime.

I exposed this beforte summer (now is sammer in Spain) and now I will 
begin working on this. By now you can try to link the modules manually 
and link them correctly.



Hudson Reis wrote:

>Hi all,
>
>I'm had problems using string. When I use the verb string in a shared library it isn't work(isn't called from a main program).
>
>I'm attaching the programs below:
>
>sgc0000a.cob -> main program. (should be compiled as a binary)
>sgc0000b.cob -> subprogram.   (should be compiled as a shared library)
>
>Thanks.
>Hudson
>  
>


-- 
Salutacions / Regards
+---------------------------------------------------------------+
| Ferran Pegueroles Forcadell                                   |
| mailto:fer...@re...                          |
| Tels (+34)937252106 - (+34)667658535                          |
| C/Unió 44 2n 2a 08201 Sabadell (BCN)                          |
+---------------------------------------------------------------+

Re: [Tiny-cobol-users] How to reduce the time for found a shared library ?

[Ferran P. F. <fer...@re...>]

On dv, 2002-08-23 at 15:19, Peter Burgess wrote:
> Hi=20
>=20
> Thanks for the information, what I would dont want to
> do is convert to the Eloquence db I want to go with an
> open source version, I was wondering what anyone else
> had used apart from the Postgresql mentioned below.
> This site was what interested me in the first place to
> using Tiny Cobol but does not have much in there yet !
>=20

There are 2 ways to use a free database with TC. The first is what you
have done with TC, use a wraper to access the C function calls of the C
API from cobol. This way you can use PostgreSQL or MySQL.

Another way is to use a SQL preprocesor. By now I think the only free
database  with a preprocesor for COBOL is firebird. I have tested it and
it works but still need some improvements, both the preprocesor and TC
to support the code generated by the preprocesor..

Can ge more info at http://www.firebird.org

Hope this helps :)

> Peter
>=20
>  --- Ferran Pegueroles Forcadell
> <fer...@re...> wrote: > On dv,
> 2002-08-23 at 10:23, Peter Burgess wrote:
> > > I am looking for some general librarys for
> > accessing
> > > databases using Tiny Cobol. Starting my first
> > hp3000
> > > conversion to Linux/Tiny Cobol , does anyone have
> > any
> > > resources they can point to that will work with an
> > sql
> > > db please.=20
> > >=20
> > Peter Osborn did a good job converting MPE/IX cobol
> > to Linux using
> > TinyCobol. They write this web to help people do the
> > same.
> >=20
> > http://linux.pwo.ca/
> >=20
> > This can help you as an start point. You can also
> > ask him for help.
> >=20
> > > Thanks for any help in advance.
> > >=20
> > > Regards
> > >=20
> > > Peter
> > >=20
> > >  --- Ferran Pegueroles
> > <fer...@re...>
> > > wrote: > eurlix wrote:
> > > >=20
> > > > >Hi All,
> > > > >
> > > > >I am trying to use postgreSQL with TC, using
> > > > Rildo's tdb02a.c
> > > > >compiled as a shared library.=20
> > > > >This works not too bad (thanks Rildo) but the
> > time
> > > > to start
> > > > >a program is almost TWENTY seconds.
> > > > >I think that is the time to find libpq.so in
> > > > /usr/lib/.
> > > > >I have tryed somethings like :
> > > > >- add "/usr/lib/libpq.so" in
> > TCOB_LD_LIBRARY_PATH,
> > > > >- recompile TC with libltdl,
> > > > >...
> > > > >but the time for start the program is always
> > the
> > > > same.
> > > > >
> > > > >As someone (perhaps Ferran) an idea about this
> > ?
> > > > >
> > > > >Regards,
> > > > > =20
> > > > >
> > > > Sorry for the late answer, I was on halydays.
> > > >=20
> > > > The calls to libpq are from the C source, then
> > the
> > > > TCOB_LD_LIBRARY_PATH=20
> > > > doesn't act on it. This only acts for finding
> > the
> > > > routines found on tdba.c
> > > >=20
> > > > My recomentation is, first link tdba.c with
> > libpq.
> > > > This can be done=20
> > > > easily because shared libs can be linked with
> > other
> > > > shared libs. This=20
> > > > should reduce the time needed to find libpq.=20
> > Then
> > > > the problem is the=20
> > > > time to fund the libraries found on tdb02a. A
> > good
> > > > solution is to rename=20
> > > > the shared object to something like libtdba.so.
> > > >=20
> > > > If this doesn't work try to inser displays and
> > > > printf on the cobol and c=20
> > > > source and see where is the time spend exactly.
> > > >=20
> > > > If nothing helps, ask me again with more
> > detailed
> > > > info.
> > > >=20
> > > > --=20
> > > > Salutacions / Regards
> > > >
> > >
> >
> +---------------------------------------------------------------+
> > > > | Ferran Pegueroles Forcadell                  =20
> >   =20
> > > >            |
> > > > | mailto:fer...@re...         =20
> >   =20
> > > >            |
> > > > | Tels (+34)937252106 - (+34)667658535         =20
> >   =20
> > > >            |
> > > > | C/Uni=F3 44 2n 2a 08201 Sabadell (BCN)         =20
> >   =20
> > > >            |
> > > >
> > >
> >
> +---------------------------------------------------------------+
> > > >=20
> > > >=20
> > > >=20
> > > >=20
> > > >
> > >
> >
> -------------------------------------------------------
> > > > This sf.net email is sponsored by: OSDN - Tired
> > of
> > > > that same old
> > > > cell phone?  Get a new here for FREE!
> > > >
> > >
> >
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> > > > _______________________________________________
> > > > Tin...@li...
> > > >
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
> >=20
> > >=20
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Everything you'll ever need on one web page
> > > from News and Sport to Email and Music Charts
> > > http://uk.my.yahoo.com
> > >=20
> > >=20
> > >
> >
> -------------------------------------------------------
> > > This sf.net email is sponsored by: OSDN - Tired of
> > that same old
> > > cell phone?  Get a new here for FREE!
> > >
> >
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> > > _______________________________________________
> > > Tin...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users
> >=20
> >=20
> >=20
> >
> -------------------------------------------------------
> > This sf.net email is sponsored by: OSDN - Tired of
> > that same old
> > cell phone?  Get a new here for FREE!
> >
> https://www.inphonic.com/r.asp?r=3Dsourceforge1&refcode1=3Dvs3390
> > _______________________________________________
> > Tin...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/tiny-cobol-users=20
>=20
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com