runtime definition of the symbol was not found.

[adrian]

When running our EOD of day and we keep getting these errors (see
below). Looks like Jbase 4.1.4.19 can't find the path to the lib. Any
ideas to stop this happening

jsh ~ -->
jsh ~ -->jshow -c EOD.FHK.INTEREST.COLLECTION
Subroutine:
/local/globus/ontwdlb_jb/bnk/bnk.run/lib/lib32.so.152
jBC EOD.FHK.INTEREST.COLLECTION version 4.1 Wed
Mar 8 07:3
2:16 2006
jBC EOD.FHK.INTEREST.COLLECTION source file DLB.BP
jsh ~ -->

jBASE: /local/globus/ontwdlb_jb/bnk/bnk.run/lib/lib32.so.152: rtld:
0712-001 Sym
bol JLibEmulateRuntime was referenced
from module
/local/globus/ontwdlb_jb/bnk/bnk.run/lib/lib32.so.152(), but a
runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol JLibCGOSUB_STACK_EMPTY_V was referenced
from module
/local/globus/ontwdlb_jb/bnk/bnk.run/lib/lib32.so.152(), but a
runtime definition
of the symbol was not found.
rtld: 0712-001 Symbol JLibCGOSUB_VI was referenced
from module
/local/globus/ontwdlb_jb/bnk/bnk.run/lib/lib32.so.152(), but a
runtime definition
of the symbol was not found.
** Error [ SUBROUTINE_CALL_FAIL ] **
Unable to perform CALL to subroutine EOD.FHK.INTEREST.COLLECTION , Line
109 ,
Source B.PROCESS.CONTROL
Press C to continue or Q to quit
Trap from an error message, error message name = SUBROUTINE_CALL_FAIL
Source changed to ./B.PROCESS.CONTROL
jBASE debugger->Q
Are you sure ?Y

[mike ryder]

Hi Adrian,

I think the message is taking you off in the wrong direction. ;-)
This is more than likely a coding problem in how you are running this
particular process in batch. It could also be that another subroutine
has been catalogued where the file name is different from the name in
the SUBROUTINE line - this always screws the lib.

hth
mike

[Greg Cooper]

The binaries of 4.1 and anything before that are incompatible. It looks like the shared library lib32.so.152 has a mix of 4.1 and pre-4.1 objects.

 

The thing to do is to completely clean out the bin and lib directories and re-CATALOG everything from scratch.

 

Of course while in the process of CATALOGing programs, ensure all these programs have been recompiled under 4.1 and there aren't any old objects hanging around from pre-4.1 days. Sometimes it is found that an old program only has the object remaining and so never gets re-compiled and then there are problems with CATALOG of objects from different jBASE releases. It only takes a single old pre-4.1 object hanging around to give these problems.

 

In short... clear all the bin , lib and every object you can find (those beginning with $ and those ending with .o) and re-BASIC/CATALOG the works. They your problem should go away and you shouldn't have any future problems.

adrian <ar_at...@yahoo.com> wrote:

[Pawel]

Hi!

Just my 2 cents :) Look at the "missing" symbols. Loader was not able to
find jbase library symbols. Is this library (libjbase.so if I remember well)
seen in loader's path? ;) That would be my first try... Is your jBASE
installation complete? Do you have similar problems with regular jBASE
programs?

Regards
Pawel

[adrian]

Thks for the advise , will give it a go

Regards
Adrian