Bug 5766 – undefined reference to `_D3std4bind12__ModuleInfoZ'
Status
RESOLVED
Resolution
DUPLICATE
Severity
regression
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
Other
OS
Linux
Creation time
2011-03-22T01:17:00Z
Last change time
2011-09-06T01:24:59Z
Assigned to
nobody
Creator
changlon
Comments
Comment #0 by changlon — 2011-03-22T01:17:19Z
I am not sure this is a dmd or phobos bug, I use dmd 2.052 build and pass this in windows, I use gdc v2 build this on linux, and all code is execute correct but cat a Segmentation fault at /lifetime.d:1122 ( see https://bitbucket.org/goshawk/gdc/issue/171/segmentation-fault-on-linux) .
I build this project on linux 32 and 64 version both cacht this error , the dmd version is dmd2.052 release and download form ftp.digitalmars.com
jade2test.o:(.data+0x197c): undefined reference to `_D3std4bind12__ModuleInfoZ'
collect2: ld returned 1 exit status
--- errorlevel 1
the source code is here :
http://gool.googlecode.com/files/jade_dmd_bug.tar.bz2
Comment #1 by changlon — 2011-03-22T01:41:18Z
I am wrong about the windows can pass this , I am not woring on windows recently . The latest time I check it still build and pass on windows .
Now I check agian , The windows throw the same error like GDC dose ,
Unhandled Exception: EXCEPTION_ACCESS_VIOLATION(0xc0000005) at _rt_finalize (0x0045db0e) thread(1256)
->Unhandled Exception: EXCEPTION_ACCESS_VIOLATION(0xc0000005) at _rt_finalize (0x0045db0e) thread(1256) .
Comment #2 by clugdbug — 2011-08-16T00:48:31Z
This bug report is incomprehensible to me.
What's the bug? Is it the segfault in lifetime.d? Or the linker error?
How was it built on Windows? The build script seems not be valid for Windows.
Also the source is huge. Please reduce it to a reasonably-sized test case.
Comment #3 by clugdbug — 2011-09-06T01:24:59Z
Bug 6014 has the same test case, and unlike this bug report, it makes sense.
*** This issue has been marked as a duplicate of issue 6014 ***