www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Out-of-date minit.obj in 2.054 zip

reply "Nick Sabalausky" <a a.a> writes:
The file "dmd2\src\druntime\src\rt\minit.obj" in the 2.054 zip is out of 
date WRT the matching asm file. (At least as far as the timestamps, I don't 
know about the actual file content.) On systems without masm386 installed, 
this causes automated DMD builders to fail without manual user intervention. 
Is it too late to get that fixed?
Jul 30 2011
next sibling parent reply Walter Bright <newshound2 digitalmars.com> writes:
On 7/30/2011 3:50 PM, Nick Sabalausky wrote:
 The file "dmd2\src\druntime\src\rt\minit.obj" in the 2.054 zip is out of
 date WRT the matching asm file. (At least as far as the timestamps, I don't
 know about the actual file content.) On systems without masm386 installed,
 this causes automated DMD builders to fail without manual user intervention.
 Is it too late to get that fixed?

Just do a 'touch' on the minit.obj.
Jul 30 2011
parent reply "Nick Sabalausky" <a a.a> writes:
"Walter Bright" <newshound2 digitalmars.com> wrote in message 
news:j12ubk$dqd$2 digitalmars.com...
 On 7/30/2011 3:50 PM, Nick Sabalausky wrote:
 The file "dmd2\src\druntime\src\rt\minit.obj" in the 2.054 zip is out of
 date WRT the matching asm file. (At least as far as the timestamps, I 
 don't
 know about the actual file content.) On systems without masm386 
 installed,
 this causes automated DMD builders to fail without manual user 
 intervention.
 Is it too late to get that fixed?

Just do a 'touch' on the minit.obj.

That's no good for an automated DMD-building tool. If the automated tool does the "touch", then if someone changes minit.asm, the obj will never get rebuilt. The "touch" would have to be left up to the user to do manually.
Jul 31 2011
parent reply Don <nospam nospam.com> writes:
Nick Sabalausky wrote:
 "Walter Bright" <newshound2 digitalmars.com> wrote in message 
 news:j12ubk$dqd$2 digitalmars.com...
 On 7/30/2011 3:50 PM, Nick Sabalausky wrote:
 The file "dmd2\src\druntime\src\rt\minit.obj" in the 2.054 zip is out of
 date WRT the matching asm file. (At least as far as the timestamps, I 
 don't
 know about the actual file content.) On systems without masm386 
 installed,
 this causes automated DMD builders to fail without manual user 
 intervention.
 Is it too late to get that fixed?


That's no good for an automated DMD-building tool. If the automated tool does the "touch", then if someone changes minit.asm, the obj will never get rebuilt. The "touch" would have to be left up to the user to do manually.

Jul 31 2011
parent "Nick Sabalausky" <a a.a> writes:
"Don" <nospam nospam.com> wrote in message 
news:j137a6$vlt$1 digitalmars.com...
 Nick Sabalausky wrote:
 "Walter Bright" <newshound2 digitalmars.com> wrote in message 
 news:j12ubk$dqd$2 digitalmars.com...
 On 7/30/2011 3:50 PM, Nick Sabalausky wrote:
 The file "dmd2\src\druntime\src\rt\minit.obj" in the 2.054 zip is out 
 of
 date WRT the matching asm file. (At least as far as the timestamps, I 
 don't
 know about the actual file content.) On systems without masm386 
 installed,
 this causes automated DMD builders to fail without manual user 
 intervention.
 Is it too late to get that fixed?


That's no good for an automated DMD-building tool. If the automated tool does the "touch", then if someone changes minit.asm, the obj will never get rebuilt. The "touch" would have to be left up to the user to do manually.


Really? I guess that solves it then.
Jul 31 2011
prev sibling parent Trass3r <un known.com> writes:
Can't we finally get rid of that asm file?
Jul 31 2011