(In reply to comment #0)
> [CODE]
> module main;
>
> import std.net.curl;
>
> void main()
> {
> }
> [/CODE]
>
> gives:
> Error 42: Symbol Undefined _D3std3net4curl12__ModuleInfoZ
I take it you are on Windows?
Follow the instructions here: http://forum.dlang.org/thread/[email protected]
This is a valid bug report. I never bothered to create it as I was actively trying to resolve it.
Comment #3 by dlang-bugzilla — 2012-04-19T09:14:53Z
SomeDude: Your comments are not helpful. Please explain why you don't consider said issue to not be a bug, since it might not be obvious to the submitter and other contributors.
I can reproduce this issue with the 2.058 zipfile release, so it is certainly a bug (although I believe it's been fixed by now).
Comment #4 by eco — 2012-04-19T09:26:17Z
(In reply to comment #3)
> SomeDude: Your comments are not helpful. Please explain why you don't consider
> said issue to not be a bug, since it might not be obvious to the submitter and
> other contributors.
>
> I can reproduce this issue with the 2.058 zipfile release, so it is certainly a
> bug (although I believe it's been fixed by now).
It remains in 2.059 unfortunately. The autotester was having difficulty loading curl and Brad Roberts and myself never did figure out why so my fix was reverted.
Comment #5 by lovelydear — 2012-04-19T09:35:46Z
OK, I'm sorry for the trouvle. I believe the bug reports should always link to the forum related discussions, else the history and some valuable bits of information are completely lost for newcomers.
Once bug reports stay in the queue forever and the history is lost, they simply stay open forever.
And I believe having enhancement requests/bugs discussed in the forums should be a requirement anyway.
For this case, I really thought it was a matter of having not linked against libcurl. Had I seen the discussion, I would have restrained myself.