[PATCH] Wrong extern(Windows) for posix _d_throw()

I'm interested how you compiled this. I've tried compiling tango as a dynamic library myself using dmd on ubuntu. This is the errors I get:

/usr/bin/ld: libtango.so: version node not found for symbol _d_throw@4
/usr/bin/ld: failed to set dynamic section sizes: Bad value

If I change "extern (Windows)" to "extern (C)" I get:

/usr/bin/ld: libtango.so: No symbol version section for versioned symbol `_d_throw@4'
/usr/bin/ld: final link failed: Nonrepresentable section on output

I think that discussion is more appropriate in bug #857. I'll post my findings about compiling tango as a shared object there so we can keep things on-topic :)

OK, this is weird. With this patch applied, now I get errors when linking using tango compiled as a static lib.

lib/libtango-basic.a(Conduit.d.o): In function `_D5tango2io6device7Conduit7Conduit5errorMFAaZv':
tango/io/device/Conduit.d:(.text._D5tango2io6device7Conduit7Conduit5errorMFAaZv+0x21): undefined reference to `_d_throw@4'
lib/libtango-basic.a(Exception.d.o): In function `onAssertError':
tango/core/Exception.d:(.text.onAssertError+0x2e): undefined reference to `_d_throw@4'
lib/libtango-basic.a(Exception.d.o): In function `onAssertErrorMsg':
tango/core/Exception.d:(.text.onAssertErrorMsg+0x34): undefined reference to `_d_throw@4'
lib/libtango-basic.a(Exception.d.o): In function `onArrayBoundsError':
tango/core/Exception.d:(.text.onArrayBoundsError+0x26): undefined reference to `_d_throw@4'
lib/libtango-basic.a(Exception.d.o): In function `onFinalizeError':
tango/core/Exception.d:(.text.onFinalizeError+0x1f): undefined reference to `_d_throw@4'
lib/libtango-basic.a(Exception.d.o):tango/core/Exception.d:(.text.onOutOfMemoryError+0xa): more undefined references to `_d_throw@4' follow
collect2: ld returned 1 exit status
--- errorlevel 1

This is really odd, extern (Windows) in POSIX? WTF! =)

I wonder if the declared argument types are simply wrong for the platform?

Here is the problem: http://d.puremagic.com/issues/show_bug.cgi?id=4398

dmd always uses Windows name mangling for _d_throw


When calling _d_throw dmd always uses the name _d_throw@4 regardless of the
operating system. Dynamic ELF libraries support versioning symbols using the
syntax name@version. Therefore when ld encounters _d_throw@4 it reads "symbol
_d_throw, version 4" and complains that there is no version 4. As long as this
isn't fixed Dynamic D libraries can't be created on operating systems using ELF
executables.

For more details, see the bug report...

I think this could not be fixed until DMD is fixed.