July 30, 2011
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?


July 31, 2011
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.
July 31, 2011
"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.


July 31, 2011
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?
>>>
>>>
>> 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.
> 
> 
Nobody should ever change minit.asm.
July 31, 2011
Can't we finally get rid of that asm file?
July 31, 2011
"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?
>>>>
>>>>
>>> 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.
>>
>>
> Nobody should ever change minit.asm.

Really? I guess that solves it then.


Top | Discussion index | About this forum | D home