Re: dynamic linking problem with two(!??) luaxlib funcs

[mfmorss@...]

Matt,

That worked like a charm, thank you!

Just in case any AIX types encounter this, the command to create lualib.so
is:

xlc lapi.o lcode.o ldebug.o ldo.o ldump.o lfunc.o lgc.o llex.o lmem.o
lobject.o lopcodes.o lparser.o lstate.o lstring.o ltable.o ltm.o lundump.o
lvm.o lzio.o lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o loslib.o
ltablib.o lstrlib.o loadlib.o linit.o -G -bexpall -o liblua.so

Then when I create some.so I just link with:

-Lpath_to_liblua -llua

and the offending functions are now recognized.

Thanks again!

Mark F. Morss
Principal Analyst, Market Risk
American Electric Power



                                                                           
             Matt Campbell                                                 
             <mattc@freedombox                                             
             .cc>                                                       To 
             Sent by:                  Lua list                            
             lua-bounces@bazar         <lua@bazar2.conectiva.com.br>       
             2.conectiva.com.b                                          cc 
             r                                                             
                                                                   Subject 
                                       Re: dynamic linking problem with    
             02/24/2006 03:40          two(!??) luaxlib funcs              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
                 Lua list                                                  
             <lua@bazar2.conec                                             
               tiva.com.br>                                                
                                                                           
                                                                           




You would not link every future shared library against liblua.a; you
would link them against liblua.so (which may be a symlink to
liblua.so.5.1 or somesuch).  Whether you have to specify the path to
liblua.so on the command line probably depends on the linker.  I know
nothing about AIX, but with the GNU linker, if you specify -llua, the
linker first looks for liblua.so, then liblua.a.  If that's not so with
the AIX linker, then you'll probably have to specify the path to
liblua.so when building shared libraries.

--
Matt Campbell
Lead Programmer
Serotek Corporation
www.freedombox.info
"The Accessibility Anywhere People"