Knowing that every time I upgrade to the latest "official" D compiler I run in to trouble:



Win32\Debug DMD\test.obj(test)
 Error 42: Symbol Undefined _D3std8datetime7SysTime8toStringMxFNbNfZAya (const(nothrow @safe immutable(char)[] function()) std.datetime.SysTime.toString)
Win32\Debug DMD\test.obj(test)
 Error 42: Symbol Undefined _D3std8datetime7SysTime6toHashMxFNaNbNiNfZk (const(pure nothrow @nogc @safe uint function()) std.datetime.SysTime.toHash)
Win32\Debug DMD\test.obj(test)
 Error 42: Symbol Undefined _D3std8datetime7SysTime8opEqualsMxFNaNbNfKxS3std8datetime7SysTimeZb (const(pure nothrow @safe bool function(ref const(std.datetime.SysTime))) std.datetime.SysTime.opEquals)
Win32\Debug DMD\test.obj(test)
 Error 42: Symbol Undefined _D3std8datetime7SysTime8__xopCmpFKxS3std8datetime7SysTimeKxS3std8datetime7SysTimeZi (int std.datetime.SysTime.__xopCmp(ref const(std.datetime.SysTime), ref const(std.datetime.SysTime)))
Win32\Debug DMD\test.obj(test)
 Error 42: Symbol Undefined _D3gtk3All12__ModuleInfoZ (gtk.All.__ModuleInfo)
\GtkD\x86\gtkd.lib(AboutDialog)
 Error 42: Symbol Undefined _D3std6format64__T14formatIntegralTS3std5array17__T8AppenderTAyaZ8AppenderTmTaZ14formatIntegralFNaNbNfS3std5array17__T8AppenderTAyaZ8AppenderxmKxS3std6format18__T10FormatSpecTaZ10FormatSpeckmZv (pure nothrow @safe void std.format.formatIntegral!(std.array.Appender!(immutable(char)[]).Appender, ulong, char).formatIntegral(std.array.Appender!(immutable(char)[]).Appender, const(ulong), ref const(std.format.FormatSpec!(char).FormatSpec), uint, ulong))
\GtkD\x86\gtkd.lib(AboutDialog)
 Error 42: Symbol Undefined _D3std5stdio6stderrS3std5stdio4File (std.stdio.File std.stdio.stderr)
\GtkD\x86\gtkd.lib(Implement)
 Error 42: Symbol Undefined _D3std6format64__T14formatUnsignedTS3std5array17__T8AppenderTAyaZ8AppenderTmTaZ14formatUnsignedFNaNbNfS3std5array17__T8AppenderTAyaZ8AppendermKxS3std6format18__T10FormatSpecTaZ10FormatSpeckbZv (pure nothrow @safe void std.format.formatUnsigned!(std.array.Appender!(immutable(char)[]).Appender, ulong, char).formatUnsigned(std.array.Appender!(immutable(char)[]).Appender, ulong, ref const(std.format.FormatSpec!(char).FormatSpec), uint, bool))
Error: linker exited with status 8
Building Win32\Debug DMD\test.exe failed!


I recompiled gtkD with the new compiler, same result.  My code was working before the upgrade just fine and I did not change anything.

And yes, I'm using the correct phobos(the one that came with dmd2).

On 07/26/2017 08:34 PM, FoxyBrown wrote:
> Knowing that every time I upgrade to the latest "official" D compiler I
> run in to trouble:
>
>
>
> Win32\Debug DMD\test.obj(test)
>  Error 42: Symbol Undefined _D3std8datetime7SysTime8toStringMxFNbNfZAya
> (const(nothrow @safe immutable(char)[] function())
> std.datetime.SysTime.toString)
> Win32\Debug DMD\test.obj(test)

Somebody else had the same problem which they solved by removing "entire dmd":

  http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org

Ali

On Thursday, 27 July 2017 at 03:41:06 UTC, Ali Çehreli wrote:
> On 07/26/2017 08:34 PM, FoxyBrown wrote:
>> Knowing that every time I upgrade to the latest "official" D compiler I
>> run in to trouble:
>>
>>
>>
>> Win32\Debug DMD\test.obj(test)
>>  Error 42: Symbol Undefined _D3std8datetime7SysTime8toStringMxFNbNfZAya
>> (const(nothrow @safe immutable(char)[] function())
>> std.datetime.SysTime.toString)
>> Win32\Debug DMD\test.obj(test)
>
> Somebody else had the same problem which they solved by removing "entire dmd":
>
>   http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>
> Ali

Thanks, that was it. So I guess I have to delete the original dmd2 dir before I install each time... didn't use to have to do that.

On 07/26/2017 09:20 PM, FoxyBrown wrote:

>> Somebody else had the same problem which they solved by removing
>> "entire dmd":
>>
>>   http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>>
>> Ali
>
> Thanks, that was it. So I guess I have to delete the original dmd2 dir
> before I install each time... didn't use to have to do that.

Normally, it shouldn't be necessary. The splitting of the datetime package[1] had this effect but I'm not sure why the installation process can't take care of it.

Ali

[1] http://dlang.org/changelog/2.075.0.html#split-std-datetime

On Wednesday, July 26, 2017 22:29:00 Ali Çehreli via Digitalmars-d-learn wrote:
> On 07/26/2017 09:20 PM, FoxyBrown wrote:
>  >> Somebody else had the same problem which they solved by removing
>  >>
>  >> "entire dmd":
>  >>   http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>  >>
>  >> Ali
>  >
>  > Thanks, that was it. So I guess I have to delete the original dmd2 dir
>  > before I install each time... didn't use to have to do that.
>
> Normally, it shouldn't be necessary. The splitting of the datetime package[1] had this effect but I'm not sure why the installation process can't take care of it.
>
> Ali
>
> [1] http://dlang.org/changelog/2.075.0.html#split-std-datetime

It _should_ take care of it. The fact that multiple people have run into this problem and that the solution was to remove dmd and then reinstall it implies that there's a bug in the installer.

- Jonathan M Davis

On Thursday, 27 July 2017 at 12:23:52 UTC, Jonathan M Davis wrote:
> On Wednesday, July 26, 2017 22:29:00 Ali Çehreli via Digitalmars-d-learn wrote:
>> On 07/26/2017 09:20 PM, FoxyBrown wrote:
>>  >> Somebody else had the same problem which they solved by removing
>>  >>
>>  >> "entire dmd":
>>  >>   http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>>  >>
>>  >> Ali
>>  >
>>  > Thanks, that was it. So I guess I have to delete the original dmd2 dir
>>  > before I install each time... didn't use to have to do that.
>>
>> Normally, it shouldn't be necessary. The splitting of the datetime package[1] had this effect but I'm not sure why the installation process can't take care of it.
>>
>> Ali
>>
>> [1] http://dlang.org/changelog/2.075.0.html#split-std-datetime
>
> It _should_ take care of it. The fact that multiple people have run into this problem and that the solution was to remove dmd and then reinstall it implies that there's a bug in the installer.
>
> - Jonathan M Davis

I do not use the installer, I use the zip file. I assumed that everything would be overwritten and any old stuff would simply go unused.. but it seems it doesn't. If the other person used the installer then it is a problem with dmd itself not designed properly and using files that it shouldn't. I simply unzip the zip file in to the dmd2 dir and replace sc.ini... that has been my MO for since I've been trying out dmd2 and only recently has it had a problem.

On 7/27/17 1:58 PM, FoxyBrown wrote:
> On Thursday, 27 July 2017 at 12:23:52 UTC, Jonathan M Davis wrote:
>> On Wednesday, July 26, 2017 22:29:00 Ali Çehreli via Digitalmars-d-learn wrote:
>>> On 07/26/2017 09:20 PM, FoxyBrown wrote:
>>>  >> Somebody else had the same problem which they solved by removing
>>>  >>
>>>  >> "entire dmd":
>>>  >> http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>>>  >>
>>>  >> Ali
>>>  >
>>>  > Thanks, that was it. So I guess I have to delete the original dmd2 dir
>>>  > before I install each time... didn't use to have to do that.
>>>
>>> Normally, it shouldn't be necessary. The splitting of the datetime package[1] had this effect but I'm not sure why the installation process can't take care of it.
>>>
>>> Ali
>>>
>>> [1] http://dlang.org/changelog/2.075.0.html#split-std-datetime
>>
>> It _should_ take care of it. The fact that multiple people have run into this problem and that the solution was to remove dmd and then reinstall it implies that there's a bug in the installer.
>>
>> - Jonathan M Davis
> 
> I do not use the installer, I use the zip file. I assumed that everything would be overwritten and any old stuff would simply go unused.. but it seems it doesn't. If the other person used the installer then it is a problem with dmd itself not designed properly and using files that it shouldn't. I simply unzip the zip file in to the dmd2 dir and replace sc.ini... that has been my MO for since I've been trying out dmd2 and only recently has it had a problem.

If you extracted the zip file over the original install, then it didn't get rid of std/datetime.d (as extracting a zipfile doesn't remove items that exist on the current filesystem but aren't in the zipfile). So I can totally see this happening.

I don't know of a good way to solve this except to tell people, don't do that.

-Steve

On Thursday, July 27, 2017 14:14:52 Steven Schveighoffer via Digitalmars-d- learn wrote:
> On 7/27/17 1:58 PM, FoxyBrown wrote:
> > I do not use the installer, I use the zip file. I assumed that everything would be overwritten and any old stuff would simply go unused.. but it seems it doesn't. If the other person used the installer then it is a problem with dmd itself not designed properly and using files that it shouldn't. I simply unzip the zip file in to the dmd2 dir and replace sc.ini... that has been my MO for since I've been trying out dmd2 and only recently has it had a problem.
>
> If you extracted the zip file over the original install, then it didn't get rid of std/datetime.d (as extracting a zipfile doesn't remove items that exist on the current filesystem but aren't in the zipfile). So I can totally see this happening.
>
> I don't know of a good way to solve this except to tell people, don't do that.

Yeah, there are plenty of releases where nothing gets removed, but files do get removed from time to time, so simply extracting the zip on top of the old directory will cause problems at least occasionally. Also, in the case of Linux, an .so is generated with a specific version number in it, so every release has different files. I don't think that Windows currently has anything like that, but it could in the future. So, if you want to use the zip, then you should always remove the old version and not simply overwrite it.

- Jonathan M Davis

On Thursday, 27 July 2017 at 18:14:52 UTC, Steven Schveighoffer wrote:
> On 7/27/17 1:58 PM, FoxyBrown wrote:
>> On Thursday, 27 July 2017 at 12:23:52 UTC, Jonathan M Davis wrote:
>>> On Wednesday, July 26, 2017 22:29:00 Ali Çehreli via Digitalmars-d-learn wrote:
>>>> On 07/26/2017 09:20 PM, FoxyBrown wrote:
>>>>  >> Somebody else had the same problem which they solved by removing
>>>>  >>
>>>>  >> "entire dmd":
>>>>  >> http://forum.dlang.org/thread/ejybuwermnentslcyajs@forum.dlang.org
>>>>  >>
>>>>  >> Ali
>>>>  >
>>>>  > Thanks, that was it. So I guess I have to delete the original dmd2 dir
>>>>  > before I install each time... didn't use to have to do that.
>>>>
>>>> Normally, it shouldn't be necessary. The splitting of the datetime package[1] had this effect but I'm not sure why the installation process can't take care of it.
>>>>
>>>> Ali
>>>>
>>>> [1] http://dlang.org/changelog/2.075.0.html#split-std-datetime
>>>
>>> It _should_ take care of it. The fact that multiple people have run into this problem and that the solution was to remove dmd and then reinstall it implies that there's a bug in the installer.
>>>
>>> - Jonathan M Davis
>> 
>> I do not use the installer, I use the zip file. I assumed that everything would be overwritten and any old stuff would simply go unused.. but it seems it doesn't. If the other person used the installer then it is a problem with dmd itself not designed properly and using files that it shouldn't. I simply unzip the zip file in to the dmd2 dir and replace sc.ini... that has been my MO for since I've been trying out dmd2 and only recently has it had a problem.
>
> If you extracted the zip file over the original install, then it didn't get rid of std/datetime.d (as extracting a zipfile doesn't remove items that exist on the current filesystem but aren't in the zipfile). So I can totally see this happening.
>
> I don't know of a good way to solve this except to tell people, don't do that.
>
> -Steve

But the issue was about missing symbols, not anything "extra". If datatime.d is there but nothing is using it, why should it matter? Why would it have any effect on the compilation process and create errors with D telling me something is being used that isn't?

dmd shouldn't be picking up extraneous and non-connected files just for the fun of it.

Basically, if no "references" escape out side of the D ecosystem, then there shouldn't be a problem.