demerphq wrote: >On 6/13/05, H.Merijn Brand <[EMAIL PROTECTED]> wrote: > > >>On Mon, 13 Jun 2005 15:41:41 -0400, vadim <[EMAIL PROTECTED]> wrote: >> >> >>>I already have a patch. >>>May be its not perfect. >>> >>> >>I'll leave it to Steve >> >> > >Please could we not forget or overlook or otherwise warnock the issue >of the /y flag on XCOPY and other aspects of the Win32 makefiles that >are included only to be able to build on operating systems that MS no >longer supports and has sent out End Of Life notices on? > >Does _anybody_ on this list build perl on pre win2k machines nowadays? > My own gut feeling is that building on Win9x/WinNT4 should still be supported. If you drop support for building on old OS's then it's not long before you also start dropping support for building with old compilers, and even VC++ 6 is getting rather old now. 7 is out and 8 is nigh if not out already. Before you know it, you won't be able to build Perl with VC++ 6. That's already happened to Parrot (the last time I tried, at least) and it really p***ed me off. I wouldn't want to see it happen to Perl too.
IIRC, Greg Matheson was on this list fairly recently, building Perl on Win98. Others may be doing likewise, but not even on this list. I'm not on any parrot mailing list, partly because I was really f***ed off that I couldn't get anywhere with it. I'll have to pull my finger out and do something about it sometime, but I might have joined in already by now if they hadn't dropped support for the "old" system that I'm running... ------------------------------------------------ Radan Computational Ltd. The information contained in this message and any files transmitted with it are confidential and intended for the addressee(s) only. If you have received this message in error or there are any problems, please notify the sender immediately. The unauthorized use, disclosure, copying or alteration of this message is strictly forbidden. Note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Radan Computational Ltd. The recipient(s) of this message should check it and any attached files for viruses: Radan Computational will accept no liability for any damage caused by any virus transmitted by this email.
