If you tell makepp, via the SHELL variable, where to find a Unix-like Shell, you don't have these worries. Those should always be portably written as dir$/command, where $/ gets replaced by a forward or backward slash, depending on the environment. While Windows programs can handle normal slashes as directory separators, this does not work for command names. A maximal use of makepp's builtin commands and embedded Perl can increase makefile portability. On Strawberry Perl with only native Windows most customary Unix commands (except GNU compilers) are missing, and the “shell” is extremely primitive. Alas this is not good enough for the repository mechanism, so that isn't available, in addition to the Cygwin deficiencies. It has a clever workaround for lack of symbolic links, namely copying instead ( &ln has stolen this idea). MinGW stays close to Windows, giving it only a Unixy look and feel. Makepp has been reorganized to much reduce this, so you may never see it. This does not seem a Perl bug, since the same perls that were error free before, now show this behaviour. In rare cases recent Cygwin also leads stat() to report a symlink for an inexistent file. Perl 5.10.1 has a problem with chmod 0 files, so they can't be used to prevent repository imports. In the long gone past, parallel builds didn't work, but it hasn't be verified which version of Cygwin or Perl made them usable. Perl 5.8.7 has a small problem with environment vars, making one test fail. When using native programs, you may need to see the note under &ln.Ĭygwin fairly closely emulates GNU/Linux and gives the best results. Here they have been tested with a minimal PATH, so as to separate them completely. There are 4 different Perl environments on Windows, which normally extend one another when installed in parallel. Click the navigation side bar's close button (×) to have more space for the table!.Often it is something that could be worked around, like compiler, operating or file system particularities or wrong environment variables. And since those test are automated on screened off machines, it can be hard to find out or even fix what is going wrong. But they give a red bar even if only one out of about hundred tests fail. Note that you get a comparable overview when going to the top right CPAN tab and choosing Perl/Platform Version Matrix ( ). We would like to hear of your results on other platforms too! This table shows with what version this has been tested where, and whether it was successful. On some platforms lacking some features, notably Cygwin, a few tests are explicitly skipped. We have a test suite of around 95 tests, all of which usually pass. We have tried to work around most of them, but a few remain. ![]() The many Perl versions available and still installed on many machines come with various subtle bugs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |