D issues are now tracked on GitHub. This Bugzilla instance remains as a read-only archive.
Issue 7561 - std.net.curl broken
Summary: std.net.curl broken
Status: RESOLVED FIXED
Alias: None
Product: D
Classification: Unclassified
Component: phobos (show other issues)
Version: D2
Hardware: All All
: P2 normal
Assignee: No Owner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-22 02:59 UTC by Stephan Dilly
Modified: 2015-06-09 05:15 UTC (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Dilly 2012-02-22 02:59:50 UTC 
[CODE]
module main;

import std.net.curl;

void main()
{
}
[/CODE]

gives:
Error 42: Symbol Undefined _D3std3net4curl12__ModuleInfoZ
Comment 1 SomeDude 2012-04-19 09:05:47 UTC 
Not a bug.
Comment 2 Brad Anderson 2012-04-19 09:13:13 UTC 
(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/xssjmbuyombztoztwhgv@forum.dlang.org

This is a valid bug report. I never bothered to create it as I was actively trying to resolve it.
Comment 3 Vladimir Panteleev 2012-04-19 09:14:53 UTC 
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 Brad Anderson 2012-04-19 09:26:17 UTC 
(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 SomeDude 2012-04-19 09:35:46 UTC 
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.
Comment 6 Brad Anderson 2012-07-13 10:16:01 UTC 
Fixed in HEAD for upcoming DMD 2.060.