"Don" wrote in message
news:j137a6$vlt$1...@digitalmars.com...
> Nick Sabalausky wrote:
>> "Walter Bright" 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
>>>
Can't we finally get rid of that asm file?
Nick Sabalausky wrote:
"Walter Bright" 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
kno
"Walter Bright" 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
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 bu
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 intervent
