Re: luasocket doesn't build on msys/mingw

Martin Spernau <[email protected]> Thu, 18 Mar 2004 08:49:03 +0100
Newsgroups gmane.comp.lang.lua.luacheia
Message-ID <[email protected]>
Hi Doug,
I'm getting the sinking feeling you are experiencing some kind of 
version related problem. I see you are using very current MinGW setup.
The setup I am working with says it's
$ gcc -v
gcc version 3.2 (mingw special 20020817-1)

I'm not sure what setup Thatcher is using, but I'm guessing it's 3.2 
something also...

Thanks very much for your report so far, I'll see if I can reproduce the 
errors you are seeing with a newer MinGW setup.

thanks, Martin



Doug Currie wrote:

>Proceeding past luacom (by forcing the rebuild of the Makefile by
>editing out the '#' in the Makefile target and doing 'make Makefile'
>in src/modules/luacom)... I am now having trouble with luasocket.
>
>Luasocket doesn't make a .dll -- I get the warnings below. Does anyone
>know why the DLL isn't built? libws2_32.a exists in mingw (perhaps the
>double slash in the last line of the first Warning below is a clue?).
>
>/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)
>rm url.lob ftp.lob smtp.lob http.lob code.lob select.lob auxiliar.lob concat.lob
>make[4]: Leaving directory `/home/e/luacheia5-5.0.1a5/src/modules/socket'
>
>Build details, FYI:
>
>Windows XP
>msys 1.0.10rc5
>MinGW-3.1.0-1.exe plus
>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
>
>Thanks.
>
>e
>
>
>
>-------------------------------------------------------
>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
>_______________________________________________
>Luacheia-list mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/luacheia-list
>
>
>  
>




-------------------------------------------------------
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