Re: [Tiny-cobol-users] Error while loading shared libraries (was: Your COBOL G/L etc. system)

[vince c. <vb...@bt...>]

Hi;

On Friday 29 December 2006 07:36, David Essex wrote:
> Vince Coen wrote:
>  > I Have now installed tc .63  but getting a lot of errors.
>  > Can't run the test_suite without a lot of errors.
>  > Ditto when compiling hello world.
>  > Can someone help?
>  > ...
>  > When running ./hello
>  >
>  > It gives me:
>  >
>  > ./hello: error while loading shared libraries:
>  > libhtcobol.so.0: cannot open
>  > shared object file: No such file or directory
>
> This seams to be a very common problem for some reason.
>
> The linker needs to locate the RT shared library 'libhtcobol.so.0'.
>
> The TC configure will install to a prefix='/usr/local' by default, so
> the shared library 'libhtcobol.so.0' should be located in the
> 'usr/local/lib' directory.

Yep, its in /usr/local/lib as in:
[vince@study ~]$ ls -la /usr/local/lib/libhtcobol.*
-rwxr-xr-x 1 root root 152812 Dec 27 22:40 /usr/local/lib/libhtcobol.a*
lrwxrwxrwx 1 root root     35 Dec 27 
16:22 /usr/local/lib/libhtcobol.so -> /usr/local/lib/libhtcobol.so.0.63.0*
lrwxrwxrwx 1 root root     35 Dec 27 
16:22 /usr/local/lib/libhtcobol.so.0 -> /usr/local/lib/libhtcobol.so.0.63.0*
-rwxr-xr-x 1 root root 153405 Dec 27 
16:22 /usr/local/lib/libhtcobol.so.0.63.0*
[vince@study ~]$ 


>
> Unfortunatly, some of the distributions do not use the 'usr/local ...'
> directories, thus the linker is not set up to search that path.
>
> So you can you can do either of the following:
>
> 1) Set the 'LD_LIBRARY_PATH' enviroment variable (bash: export
> LD_LIBRARY_PATH=usr/local/lib), which is a temporary solution.

Now done that.

> 2) Use the 'ldconf' command to add the path to the linker search path.

I do not seem to have that command. Where is it from?

> 3) Configure TC using the `--prefix=/usr' option, then compile and
> install it.

have added --prefix=/usr/local

>  > I need to solve this first before attempting the
>  > test suite again as most of
>  > the test produce similar to this:
>  > ...
>
> The test suite on version 0.63 is set up to expect to find the compiler,
> RTL and resouce files in the source code sub-directories above the
> 'test_suite' directory (i.e. ../compiler, ../lib, etc.).
>
> So it is best to just configure and compiler TC, then run the test suite.
> Otherwise, modifications to the perl script are required.

Nope, on this you have lost me. I understand the bit about modding the perl 
script though.

>
> Hint: Before you run the test suite, remove the RT shared library (and
> links) or compile the RTL a static library only.

Lost me on this as well.

I'm assuming the RT shared libs are similar to MF?  Allowing for strong Ram 
facilities Can I not just compile the whole program to link all required 
modules and libraries together and would this be the fastest way to load and 
run?

Also using the configure option of MF compatable what exactly does this do?

I cannot see any documentation on this or what language set is available in 
the compiler at this time.

Is the CVS version more up to date and reasonably stable or is it best to 
stick to the archives in the download area?

Out of interest what problems would there be to use tc on a 64 bit system 
i.e., Dual 2 core E6600 using a mandriva x86-64 Linux system install (It uses 
both 32 and 64 bit libraries?

Vince.