Re: Problems compiling luacheia with Mingw

Well, I tried a build from the CVS.

Reminder, my environment is:
Windows XP
msys 1.0.10
mingw gcc-core-3.3.3-20040217-1.tar.gz
mingw gcc-g++-3.3.3-20040217-1.tar.gz
mingw binutils-2.15.90-20040222-1.tar.gz

After the checkout I did:

./configure --enable-modules='bit lxp socket'
make

The make completed, but as before the luasocket.dll was not built; the
relevant part of the console output is below.

Then I did a

make install

It failed to install lualib and exited. Again, the console output is below.

I am stumped, and am giving up. I can build and install all the pieces
with mingw/msys and the original distributions (lua, luasockets, etc.)
with minor Makefile target additions for DLLs. The Luacheia
distribution just isn't helping me at all at this point. Not only is
the libtool build *much* slower than a simple Makefile build, but it
just doesn't work for me. Perhaps Hamster will be the answer.

Regards,

e

###################  make (partial)

/bin/sh ../../../libtool --mode=link gcc -DLUASOCKET_COMPILED -DINET_ATON=1 -g 
-O2   -o luasocket.la -rpath /usr/local/lib/luacheia5 -module -avoid-version 
-no-undefined luasocket.lo timeout.lo buffer.lo io.lo auxiliar.lo select.lo 
inet.lo tcp.lo udp.lo socket_loadmodule.lo wsocket.lo  -L../../../lua-5.0-proxy 
-llua -llualib  -lws2_32

*** Warning: linker path does not have real file for library -lws2_32.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libws2_32 and none of the candidates passed a file format test
*** using a file magic. Last file checked: /mingw/lib//libws2_32.a

*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module luasocket.  Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.
ar cru .libs/luasocket.a  luasocket.o timeout.o buffer.o io.o auxiliar.o 
select.o inet.o tcp.o udp.o socket_loadmodule.o wsocket.o
ranlib .libs/luasocket.a
creating luasocket.la
(cd .libs && rm -f luasocket.la && ln -s ../luasocket.la luasocket.la)
make[4]: Leaving directory `/home/e/Luacheia-head/luacheia/src/modules/socket'

###################  make install

e-qohR+lvoKGE@xxxxxxxxxxxxxxxx ~/Luacheia-head/luacheia
$ make install
Making install in lua-utils
make[1]: Entering directory `/home/e/Luacheia-head/luacheia/lua-utils'
make[2]: Entering directory `/home/e/Luacheia-head/luacheia/lua-utils'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/e/Luacheia-head/luacheia/lua-utils'
make[1]: Leaving directory `/home/e/Luacheia-head/luacheia/lua-utils'
Making install in lua-5.0-proxy
make[1]: Entering directory `/home/e/Luacheia-head/luacheia/lua-5.0-proxy'
make[2]: Entering directory `/home/e/Luacheia-head/luacheia/lua-5.0-proxy'
/bin/sh ../mkinstalldirs /usr/local/lib
 /bin/sh ../libtool --mode=install /bin/install -c  liblua.la 
/usr/local/lib/liblua.la
/bin/install -c .libs/liblua.dll.a /usr/local/lib/liblua.dll.a
base_file=`basename ${file}`
 dlpath=`/bin/sh 2>&1 -c '. .libs/'${base_file}'i;echo $dlname'`
 dldir=/usr/local/lib/`dirname $dlpath`
 test -d $dldir || mkdir -p $dldir
 /bin/install -c .libs/liblua-5.dll $dldir/liblua-5.dll
/bin/install -c .libs/liblua.lai /usr/local/lib/liblua.la
/bin/install -c .libs/liblua.a /usr/local/lib/liblua.a
ranlib /usr/local/lib/liblua.a
chmod 644 /usr/local/lib/liblua.a
----------------------------------------------------------------------
Libraries have been installed in:
   /usr/local/lib

If you ever happen to want to link against installed libraries
in a given directory, LIBDIR, you must either use libtool, and
specify the full pathname of the library, or use the `-LLIBDIR'
flag during linking and do at least one of the following:
   - add LIBDIR to the `PATH' environment variable
     during execution
   - add LIBDIR to the `LD_RUN_PATH' environment variable
     during linking
   - use the `-Wl,--rpath -Wl,LIBDIR' linker flag

See any operating system documentation about shared libraries for
more information, such as the ld(1) and ld.so(8) manual pages.
----------------------------------------------------------------------
 /bin/sh ../libtool --mode=install /bin/install -c  liblualib.la 
/usr/local/lib/liblualib.la
libtool: install: warning: relinking `liblualib.la'
(cd /home/e/Luacheia-head/luacheia/lua-5.0-proxy; /bin/sh ../libtool 
--mode=relink gcc "-DLUA_API=__declspec(dllexport)" -DUSE_DLL=1 -g -O2 -o 
liblualib.la -rpath /usr/local/lib -version-info 5:0:0 -no-undefined lauxlib.lo 
lbaselib.lo ldblib.lo liolib.lo lmathlib.lo lstrlib.lo ltablib.lo loadlib.lo 
-L. -llua )

*** Warning: linker path does not have real file for library -llua.
*** I have the capability to make that library automatically link in when
*** you link to this library.  But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with liblua and none of the candidates passed a file format test
*** using a file magic. Last file checked: /usr/local/bin/liblua-5.dll
*** The inter-library dependencies that have been dropped here will be
*** automatically added whenever a program is linked with this library
*** or is declared to -dlopen it.

*** Since this library must not contain undefined symbols,
*** because either the platform does not support them or
*** it was explicitly requested with -no-undefined,
*** libtool will only create a static version of it.
ar cru .libs/liblualib.a  lauxlib.o lbaselib.o ldblib.o liolib.o lmathlib.o 
lstrlib.o ltablib.o loadlib.o
ranlib .libs/liblualib.a
creating liblualib.la
(cd .libs && rm -f liblualib.la && ln -s ../liblualib.la liblualib.la)
/bin/install -c .libs/liblualib.dll.aT /usr/local/lib/liblualib.dll.a
/bin/install: cannot stat `.libs/liblualib.dll.aT': No such file or directory
make[2]: *** [install-libLTLIBRARIES] Error 1
make[2]: Leaving directory `/home/e/Luacheia-head/luacheia/lua-5.0-proxy'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/e/Luacheia-head/luacheia/lua-5.0-proxy'
make: *** [install-recursive] Error 1


Wednesday, March 24, 2004, 4:12:53 PM, Martin wrote:

> Ok, I did some testing:
> first I updated my CVS workdir to the current version.

> I did
> ./configure && make && make install
> to see that everything still worked, which it did.

> Now I copied the contents of
> gcc-core-3.3.3-20040217-1.tar.gz
> over my MinGW installation (which was 3.2 based)
> again
> ./configure && make && make install
> BANG! LuaCOM failed the make phase miserably where it would at least 
> build w/ lots of warnings before

> Then I tried
>  ./configure --enable-modules='socket lxp'
> to avoid LuaCOM, and then
> make && make install
> Now that seems to work ok

> So I can now reproduce Doug's first error about LuaCOM, but not the 
> 'make install' problem...
> (I'm working on win2k)

> BTW:
> I vote we disable default building of LuaCOM for now, as we are using 
> some not-really-uptodate version of it... And other opinions?

> -Martin



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click