Re: std.socket with GDC
On Sunday, 26 February 2012 at 02:01:17 UTC, Andrew Wiley wrote: I recall having some issues because Winsock needs to be on the linker commandline *after* phobos. Try running with `gdc -v` to see what the linker commandline looks like. That's it... any way to get it in the correct order, without having to call the linker separately? :/
Re: std.socket with GDC
On Sat, Feb 25, 2012 at 4:45 PM, DNewbie wrote: > > > On Sat, Feb 25, 2012, at 10:38 PM, Mars wrote: >> On Saturday, 25 February 2012 at 18:27:29 UTC, Vladimir Panteleev >> wrote: >> > On Friday, 24 February 2012 at 19:15:26 UTC, Mars wrote: >> >> Hello everybody. >> >> >> >> When trying to compile a program using GDC (Windows), which >> >> includes an import std.socket, I get a lot "undefined >> >> reference"s, like >> >>>undefined reference to `WSAGetLastError@0' >> > >> > Try linking with libws2_32.a. >> >> Still the same. Does that work for you? >> > > std.socket works for me, > gdc64 (windows) I recall having some issues because Winsock needs to be on the linker commandline *after* phobos. Try running with `gdc -v` to see what the linker commandline looks like.
Re: std.socket with GDC
On Sat, Feb 25, 2012, at 10:38 PM, Mars wrote: > On Saturday, 25 February 2012 at 18:27:29 UTC, Vladimir Panteleev > wrote: > > On Friday, 24 February 2012 at 19:15:26 UTC, Mars wrote: > >> Hello everybody. > >> > >> When trying to compile a program using GDC (Windows), which > >> includes an import std.socket, I get a lot "undefined > >> reference"s, like > >>>undefined reference to `WSAGetLastError@0' > > > > Try linking with libws2_32.a. > > Still the same. Does that work for you? > std.socket works for me, gdc64 (windows)
Re: std.socket with GDC
On Saturday, 25 February 2012 at 18:27:29 UTC, Vladimir Panteleev wrote: On Friday, 24 February 2012 at 19:15:26 UTC, Mars wrote: Hello everybody. When trying to compile a program using GDC (Windows), which includes an import std.socket, I get a lot "undefined reference"s, like undefined reference to `WSAGetLastError@0' Try linking with libws2_32.a. Still the same. Does that work for you?
Re: std.socket with GDC
On Friday, 24 February 2012 at 19:15:26 UTC, Mars wrote: Hello everybody. When trying to compile a program using GDC (Windows), which includes an import std.socket, I get a lot "undefined reference"s, like undefined reference to `WSAGetLastError@0' Try linking with libws2_32.a.
std.socket with GDC
Hello everybody. When trying to compile a program using GDC (Windows), which includes an import std.socket, I get a lot "undefined reference"s, like undefined reference to `WSAGetLastError@0' By now I know this happens if there are libraries missing or similar, but seeing how this is part of Phobos, something must be wrong with the GDC Phobos lib... so the only thing that comes to my mind is recompiling that. Next problem: std\stdio.d:157: Error: static assert "unsupported C I/O system" So, I'm basically stuck. Can't use socket, can't recompile Phobos. Anybody got an idea on how to solve either problem? :P" Mars
