DMD git master stuck at 2.084???
H. S. Teoh
hsteoh at quickfur.ath.cx
Thu Sep 26 00:49:49 UTC 2019
On Wed, Sep 25, 2019 at 05:40:51PM -0700, H. S. Teoh via Digitalmars-d wrote:
> On Wed, Sep 25, 2019 at 05:29:07PM -0700, H. S. Teoh via Digitalmars-d wrote:
> > DMD64 D Compiler v2.084.0-2446-gaf585f61a
> > Copyright (C) 1999-2019 by The D Language Foundation, All Rights
> > Reserved written by Walter Bright
> OK, it gets stranger. So, I thought perhaps my git repo is somehow
> corrupted, so I nuked the whole thing and re-cloned from github, then
> ran `rdmd src/build.d`. The resulting binary produces even stranger
> output with --version now:
> DMD64 D Compiler v2.058-20347-gaf585f61a
> Copyright (C) 1999-2019 by The D Language Foundation, All Rights
> Reserved written by Walter Bright
> 2.058??! Where did that come from???
OK, I *think* I solved the mystery... the utterly evil rdmd cache!!!
I nuked the repo, did a fresh git clone, and then ran rdmd --force
src/build.d, and finally I get a sane binary:
DMD64 D Compiler v2.088.0-240-gaf585f61a
Copyright (C) 1999-2019 by The D Language Foundation, All Rights
Reserved written by Walter Bright
In retrospect, it's probably because I haven't updated my rdmd in years:
rdmd --version gives:
rdmd build 20170608
Usage: rdmd [RDMD AND DMD OPTIONS]... program [PROGRAM OPTIONS]...
Builds (with dependents) and runs a D program.
Example: rdmd -release myprog --myprogparm 5
[ ... snipped ... ]
I've no idea *what* was in the old rdmd cache... cached copies of older
compilers? Cached copies of build.d?! Whatever it was, it's truly
Perhaps the most widespread illusion is that if we were in power we would behave very differently from those who now hold it---when, in truth, in order to get power we would have to become very much like them. -- Unknown
More information about the Digitalmars-d