Thread overview
ldc2-1.1.0-beta2-win64-msvc link error with std.datetime
Aug 05, 2016
Miguel L
Aug 05, 2016
kinke
Aug 06, 2016
Chang Long
Aug 08, 2016
Kai Nacke
Aug 08, 2016
Kai Nacke
Aug 12, 2016
Kai Nacke
August 05, 2016
Hello
I am getting this link error when trying to use LDC2 to compile a program that references std.datetime. The same program compiles with no errors in DMD:

Using Visual Studio: C:\Program Files (x86)\Microsoft Visual Studio 14.0\
main.obj : error LNK2019: unresolved external symbol _D3std8datetime4Date15__invariant2044MxFNaNfZv referenced in function _Dmain
Error: `C:\windows\system32\cmd.exe /s /c "D:\LDC\ldc2-1.1.0-beta2-win64-msvc\bin\amd64.bat link.exe"` failed with status: 1120
Exit code 1120
August 05, 2016
On Friday, 5 August 2016 at 06:26:54 UTC, Miguel L wrote:
> Hello
> I am getting this link error when trying to use LDC2 to compile a program that references std.datetime. The same program compiles with no errors in DMD:
>
> Using Visual Studio: C:\Program Files (x86)\Microsoft Visual Studio 14.0\
> main.obj : error LNK2019: unresolved external symbol _D3std8datetime4Date15__invariant2044MxFNaNfZv referenced in function _Dmain
> Error: `C:\windows\system32\cmd.exe /s /c "D:\LDC\ldc2-1.1.0-beta2-win64-msvc\bin\amd64.bat link.exe"` failed with status: 1120
> Exit code 1120

Could you please give our latest CI build at https://github.com/ldc-developers/ldc/releases/tag/LDC-Win64-master a shot? Just to make sure there's nothing wrong with the beta2 package. If the CI build also fails, please try to come up with a minimal testcase (dustmite?) and either post it here in the forum, or preferrably open a new GitHub issue (https://github.com/ldc-developers/ldc/issues). Thanks!
August 06, 2016
On Friday, 5 August 2016 at 06:26:54 UTC, Miguel L wrote:
> Hello
> I am getting this link error when trying to use LDC2 to compile a program that references std.datetime. The same program compiles with no errors in DMD:
>
> Using Visual Studio: C:\Program Files (x86)\Microsoft Visual Studio 14.0\
> main.obj : error LNK2019: unresolved external symbol _D3std8datetime4Date15__invariant2044MxFNaNfZv referenced in function _Dmain
> Error: `C:\windows\system32\cmd.exe /s /c "D:\LDC\ldc2-1.1.0-beta2-win64-msvc\bin\amd64.bat link.exe"` failed with status: 1120
> Exit code 1120

OSX build with dub --force

Undefined symbols for architecture x86_64:
  "__D3std8datetime4Date15__invariant1671MxFNaNfZv", referenced from:
      __D3std8datetime4Date26__T16fromISOExtStringTAywZ16fromISOExtStringFNaNfxAywZS3std8datetime4Date in libvibe-d_data.a(vibe.data.json.o)
  "__D3std8datetime4Date15__invariant1768MxFNaNfZv", referenced from:
      __D4vibe4inet7message96__T21writeRFC822DateStringTPS4vibe5utils5array32__T13FixedAppenderHTAyaVmi16TyaZ13FixedAppenderZ21writeRFC822DateStringFNaNbKPS4vibe5utils5array32__T13FixedAppenderHTAyaVmi16TyaZ13FixedAppenderS3std8datetime4DateZv in libvibe-d_core.a(vibe.inet.message.o)
      __D4vibe4inet7message96__T21writeRFC822DateStringTPS4vibe5utils5array32__T13FixedAppenderHTAyaVmi31TyaZ13FixedAppenderZ21writeRFC822DateStringFNaNbKPS4vibe5utils5array32__T13FixedAppenderHTAyaVmi31TyaZ13FixedAppenderS3std8datetime4DateZv in libvibe-d_core.a(vibe.inet.message.o)
  "__D3std8datetime4Date15__invariant2360MxFNaNfZv", referenced from:
      __D4vibe4inet7message90__T21writeRFC822DateStringTS4vibe5utils5array27__T13AllocAppenderHTAyaTyaZ13AllocAppenderZ21writeRFC822DateStringFNbKS4vibe5utils5array27__T13AllocAppenderHTAyaTyaZ13AllocAppenderS3std8datetime4DateZv in libvibe-d_http.a(vibe.http.common.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
August 08, 2016
On Saturday, 6 August 2016 at 15:27:20 UTC, Chang Long wrote:
>
> OSX build with dub --force
>

Which project? Now we know there is a problem but we don't know how to reproduce.

Regards,
Kai
August 08, 2016
On Monday, 8 August 2016 at 20:42:17 UTC, Kai Nacke wrote:
> On Saturday, 6 August 2016 at 15:27:20 UTC, Chang Long wrote:
>>
>> OSX build with dub --force
>>
>
> Which project? Now we know there is a problem but we don't know how to reproduce.
>
> Regards,
> Kai

We appreciate every bug report but to actually fix the problem we need to reproduce it...
August 12, 2016
On Monday, 8 August 2016 at 20:45:45 UTC, Kai Nacke wrote:
> On Monday, 8 August 2016 at 20:42:17 UTC, Kai Nacke wrote:
>> On Saturday, 6 August 2016 at 15:27:20 UTC, Chang Long wrote:
>>>
>>> OSX build with dub --force
>>>
>>
>> Which project? Now we know there is a problem but we don't know how to reproduce.
>>
>> Regards,
>> Kai
>
> We appreciate every bug report but to actually fix the problem we need to reproduce it...

It's now issue #1678: https://github.com/ldc-developers/ldc/issues/1678