Anatoly Vorobey wrote: >Hello, > >perl-5.8.6 builds cleanly on Win32 with only MinGW and >dmake installed (provided it's not the latest version of dmake, >which has a little problem with makefile.mk). However, maintperl >and bleadperl don't, because change 23762 introduced a dependency on >tr, which is not present on such a system. Links: > >http://public.activestate.com/gsar/APC/diffs/23762.gz >http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-01/msg00132.html > >Change 23762 went into maintperl as part of change 23784: >http://public.activestate.com/gsar/APC/perl-5.8.x-diffs/23784.gz > > (FYI, an excellent tool for looking at changes is Rafael's perl repository browser:
http://public.activestate.com/cgi-bin/perlbrowse http://public.activestate.com/cgi-bin/perlbrowse?patch=23762 ) >This might not have come up when people tested the changes >(e.g. >http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2005-01/msg00160.html >) >because they had 'tr' in the path on their machine, from msys or cygwin. > > Yep. Guilty as charged. I will remove Cygwin from my perl build environment to be sure that doesn't happen again. >Is it possible to avoid this use of tr and/or to integrate >it into buildext.pl, to avoid the external dependency? The crucial lines >are >[...] >On a non-cygwin MinGW system, running the output of buildext.pl >--list-static-libs though 'tr \\ /' is certainly superfluous, because >the linker understands the backslashes. I don't know enough >about Cygwin to determine whether this is needed there; but if it is, >it could probably be done inside buildext.pl? > I'm never sure if the win32/makefile.mk is relevant for Cygwin or not. It is certainly not used for doing Cygwin builds, but it is possible to use MinGW from within a Cygwin environment to create a "native" Win32 build. Does anyone know if that uses win32/makefile.mk or not? Yitzchak, perhaps? - Steve ------------------------------------------------ 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.
