Mail Archives: djgpp-workers/2001/08/26/05:14:40
> > Hard to say for sure. I know inside gdb xgcc always made the ntvdm go
> > away on the third one. The test program usually didn't print anything to
> > the screen, which would indicate the first one.
>
> Not necessarily: it's possible that the DOS box went away before the
> display subsystem had a chance to run its redisplay (which only happens
> once in a while).
Agreed.
> Writing log messages to a disk file, and fsync'ing the handles, might be a
> more reliable way of tracking the execution.
If it would fail more reliably I'd test that :-)
> > I think we are randomly lucky that the name was 78 characters generated
> > by GCC build instead of 81 ...
>
> No, that's not luck: function 60h is supposed to take care of this.
> That's how longish file names work on plain DOS, although we never make
> sure they are shorter than 80 characters.
Correct. We are on the hairy edge because we have ../ in paths now. One
more and we'd be beyond the limit :-)
> > I think we would be better off finding why we get lots of ../ in 3.01 and
> > didn't get any in 2.953 ... just to be safe...
>
> That's a good thing, too; but we cannot depend on every package doing so:
> it would make the porter's job impossibly hard.
Understood, but it was working better in 2.953 ... I guess that's progress ...
- Raw text -