No joy:

====

LIH1:TSH009:/HealthMarkets/lib$
rm liblua.so
LIH1:TSH009:/HealthMarkets/lib$
lua
Lua 5.2.0  Copyright (C) 1994-2011 Lua.org, PUC-Rio
> require "cjson"
error loading module 'cjson' from file
'/HealthMarkets/lua4z/lib/lua/5.1/cjson.so':
        dynamic libraries not enabled; check your Lua installation
stack traceback:
        [C]: in ?
        [C]: in function 'require'
        stdin:1: in main chunk
        [C]: in ?
>
LIH1:TSH009:/HealthMarkets/lib$
ls -l /HealthMarkets/lua4z/lib/lua/5.1/cjson.so
-rwxr-xr-x   1 TSH009   TSHG      192512 Oct 22 22:08
/HealthMarkets/lua4z/lib/lua/5.1/cjson.so
LIH1:TSH009:/HealthMarkets/lib$

====

On Thu, Oct 23, 2014 at 9:42 AM, David Crayford <[email protected]> wrote:

> There seems to be a problem loading the SO from a symlink. Can you try it
> without a symlink? It works on my system but if I can narrow it down to
> that and recreate it at our lab I can cut a fix.
>
>
> On 23/10/2014 10:18 PM, John McKown wrote:
>
>> ​I was certain that I did something wrong, but I don't know what.
>> Somewhere
>> I have missed a step.
>>
>>  require "cjson"
>>>
>> error loading module 'cjson' from file
>> '/HealthMarkets/lua4z/lib/lua/5.1/cjson.so':
>>          dynamic libraries not enabled; check your Lua installation
>> stack traceback:
>>          [C]: in ?
>>          [C]: in function 'require'
>>          stdin:1: in main chunk
>>          [C]: in ?
>> ​
>>
>> On Thu, Oct 23, 2014 at 9:11 AM, David Crayford <[email protected]>
>> wrote:
>>
>>  I'm at a loss! Can you do this quick test for me.
>>>
>>> Invoke the Lua shell by typing lua in the shell
>>>
>>> type
>>>
>>> require "cjson"
>>>
>>> post the stack trace
>>>
>>>
>>> On 23/10/2014 9:51 PM, John McKown wrote:
>>>
>>>  On Thu, Oct 23, 2014 at 8:24 AM, David Crayford <[email protected]>
>>>> wrote:
>>>>
>>>>   Can I convince you to try it again. I've uploaded  an updated IVP.
>>>>
>>>>>
>>>>>   ​Well the install script does not give any error messages when I
>>>>> reuse
>>>>>
>>>> the
>>>> same PDSE library names. But the ivp still fails. I can't shake the
>>>> feeling
>>>> that I've done something wrong that I just can't see. Oh, I changed the
>>>> HM
>>>> to HealthMarkets. The HM is a symlink to HealthMarkets (the name of the
>>>> company). Also, for whatever it may be worth, I am running my BASH 4.2
>>>> port
>>>> as the UNIX shell. But I get the same errors when I run under /bin/sh.
>>>>
>>>> ====
>>>>
>>>> LIH1:TSH009:/home/tsh009$
>>>> printenv | grep LUA
>>>> LUA_PATH=/HealthMarkets/lua4z/share/lua/5.1/?.lua;./?.lua;/
>>>> HealthMarkets/lua4z/share/lua/5.1/?/init.lua;/HealthMarkets/
>>>> lua4z/lua/5.1/?.lua;/HealthMarkets/lua4z/install/?.lua
>>>> LUA_CPATH=./?.so;/HealthMarkets/lua4z/lib/lua/5.1/?.so
>>>> LIH1:TSH009:/home/tsh009$
>>>> lua /HealthMarkets/lua4z/examples/ivp.lua
>>>> Lua4z installation verification procedure (IVP)
>>>>
>>>> Checking LUA_PATH configuration: passed
>>>> Fail: Could not load cjson
>>>> Checking LUA_CPATH configuration: failed
>>>>
>>>> Test results:
>>>>     1 passed
>>>>     1 failed
>>>>
>>>> LIH1:TSH009:/home/tsh009$
>>>> ls -lR /HealthMarkets/lua4z/lib/lua/5.1/
>>>> /HealthMarkets/lua4z/lib/lua/5.1/:
>>>> total 16844
>>>> -rwxr-xr-x   1 TSH009   TSHG      192512 Oct 22 22:08 cjson.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      135168 Oct 22 22:08 cmsgpack.so
>>>> lrwxrwxrwx   1 TSH009   TSHG          16 Oct 23 08:35 crypto.so ->
>>>> lcrypto.so.0.3.0
>>>> -rwxr-xr-x   1 TSH009   TSHG     1241088 Oct 22 22:08 curses_c.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      126976 Oct 22 22:08 iconv.so
>>>> drwxr-xr-x   2 TSH009   TSHG         288 Sep 19 20:53 ispf
>>>> drwxr-xr-x   2 TSH009   TSHG         288 Sep 13 22:26 lanes
>>>> -rwxr-xr-x   1 TSH009   TSHG     4894720 Oct 22 22:08 lcrypto.so.0.3.0
>>>> -rwxr-xr-x   1 TSH009   TSHG      163840 Oct 22 22:08 lfs.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      278528 Oct 22 22:08 lpeg.so
>>>> drwxr-xr-x   2 TSH009   TSHG         288 Sep 13 22:26 luasql
>>>> lrwxrwxrwx   1 TSH009   TSHG          12 Oct 23 08:35 lxp.so ->
>>>> lxp.so.1.2.0
>>>> -rwxr-xr-x   1 TSH009   TSHG      503808 Oct 22 22:08 lxp.so.1.2.0
>>>> drwxr-xr-x   2 TSH009   TSHG         288 Sep 13 22:28 mime
>>>> -rwxr-xr-x   1 TSH009   TSHG      393216 Oct 22 22:08 posix_c.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      135168 Oct 22 22:08 rings.so
>>>> drwxr-xr-x   2 TSH009   TSHG         320 Sep 13 22:28 socket
>>>> drwxr-xr-x   2 TSH009   TSHG         288 Sep 13 22:27 ssl
>>>> -rwxr-xr-x   1 TSH009   TSHG      126976 Oct 22 22:08 struct.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      290816 Oct 22 22:08 zlib.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/ispf:
>>>> total 496
>>>> -rwxr-xr-x   1 TSH009   TSHG      241664 Oct 22 22:08 core.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/lanes:
>>>> total 800
>>>> -rwxr-xr-x   1 TSH009   TSHG      397312 Oct 22 00:16 core.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/luasql:
>>>> total 368
>>>> -rwxr-xr-x   1 TSH009   TSHG      180224 Oct 22 22:08 odbc.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/mime:
>>>> total 288
>>>> -rwxr-xr-x   1 TSH009   TSHG      135168 Oct 22 22:08 core.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/socket:
>>>> total 1296
>>>> -rwxr-xr-x   1 TSH009   TSHG      368640 Oct 22 22:08 core.so
>>>> -rwxr-xr-x   1 TSH009   TSHG      274432 Oct 22 22:08 unix.so
>>>>
>>>> /HealthMarkets/lua4z/lib/lua/5.1/ssl:
>>>> total 12560
>>>> -rwxr-xr-x   1 TSH009   TSHG     6422528 Oct 22 22:08 core.so
>>>> LIH1:TSH009:/home/tsh009$
>>>>
>>>>
>>>> ====​
>>>>
>>>>
>>>>
>>>>  ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to [email protected] with the message: INFO IBM-MAIN
>>>
>>>
>>
>>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>



-- 
The temperature of the aqueous content of an unremittingly ogled
culinary vessel will not achieve 100 degrees on the Celsius scale.

Maranatha! <><
John McKown

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to