Updated D then undefined symbols in vibed

[Jot via Digitalmars-d-learn]

On Thursday, 24 November 2016 at 20:18:16 UTC, Jot wrote:
> On Thursday, 24 November 2016 at 17:46:38 UTC, ag0aep6g wrote:
>> On 11/24/2016 06:15 PM, Jot wrote:
>>> I think you are failing to realize the first axiom I 
>>> presented. I only
>>> updated dmd2. This shouldn't change the object and library 
>>> files. They
>>> should essentially compile to the same thing and it shouldn't 
>>> matter.
>>
>> As far as I can tell, this isn't generally true. For example, 
>> dmd may get fixes/changes in name mangling, making it 
>> incompatible with old object files. Since you've already 
>> cleaned everything, this doesn't seem to be the issue here. 
>> But don't assume that a newer dmd is guaranteed to work with 
>> older object files. It isn't.
>
> And dmd2.exe does not recognize that an object file is out of 
> date? Seems like a bug to me...

So, the issue was I was not using phobos updated libraries.

Should dmd2.exe not complain about such things? They are easy 
checks and can solve some hard to track bugs by simply storing a 
a date in the files and comparing to what it is expecting.