Re: IUP and Ubuntu

[Dirk Laurie <dpl@...>]

On Thu, Feb 24, 2011 at 03:18:29PM +0200, Antonio Scuri wrote:
> 
>   I unpacked and tested iup-3.4_Linux26g4_lib.tar.gz but no error occurred.
> 
>   I unpacked and tested iup-3.3_Linux26g4_lib.tar.gz and the error you
> describe occurred.
> 
I had installed 3.3 before 3.4 so it is possible that the system
was still seeing it.  So after reading the above, I did the following:

1. Carefully read the 3.3 install and config_lua_module scripts.
2. Manually removed the files created by the 3.3 scripts.
3. Reran the 3.4 scripts.
4. Tried 'require "iuplua"' again.  
    This time I got an error that the module was not found.  
5. Carefully read the output from install, still visible on the terminal,
     and discovered that the files went into /usr/lib64, not /usr/lib.
6. Ran lua with an expanded package.path as follows:   

$ lua
Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
> package.path = package.path .. ";/usr/lib64/lua/5.1/?.so"
> require "iuplua"
error loading module 'iuplua' from file '/usr/lib64/lua/5.1/iuplua.so':
    /usr/lib64/lua/5.1/iuplua.so:1: unexpected symbol near 'char(127)'
stack traceback:
    [C]: ?
    [C]: in function 'require'
    stdin:1: in main chunk
    [C]: ?

7. Chaecked that the only other package on my system that uses
    /usr/lib64 is fakeroot, which I used once a long time ago.
    Removed fakeroot using aptitude, and deleted all of /usr/lib64
    recursively.
8. Reran the 3.4 scripts.    
9. Ran lua again.  No error this time:
$ lua
Lua 5.1.4  Copyright (C) 1994-2008 Lua.org, PUC-Rio
> require"iuplua"
> 
10. Tried Steve's presentation.  I'll report on that in a separate
    post.  It worked eventually.

Remarks:

1. The error was caused mainly because the test

if [ -d /usr/lib64 ]; then
  SYSTEM_LIB=/usr/lib64
else
  SYSTEM_LIB=/usr/lib
fi

is too simplistic. 

2. The typical Unix user feels disoriented if a tarball contains
    no README or INSTALL.  Some of the things the scripts say could
    usefully go in there.

3. The scripts also reported
./install: line 4: tec_uname: No such file or directory
./install: line 68: ComputeTecUname: command not found
./install: line 63: Pause: command not found
./install_dev: line 4: tec_uname: No such file or directory
./install_dev: line 71: ComputeTecUname: command not found
./install_dev: line 66: Pause: command not found
which did not cause them to fail, though. 

Dirk