X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.os2;h=1e7464bb6742583182cd0f5f5997d39f6b459570;hb=765e9edb2de192ef033766d867f9bd290e9935e9;hp=10e54cde908beba09b7da9391d4ac1a3c0219052;hpb=a7665c5ea62576c158d913778ec5f7158d35f5c4;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.os2 b/README.os2 index 10e54cd..1e7464b 100644 --- a/README.os2 +++ b/README.os2 @@ -809,10 +809,8 @@ Change to the directory of extraction. =head2 Application of the patches -You need to apply the patches in F<./os2/diff.*> and -F<./os2/POSIX.mkfifo> like this: +You need to apply the patches in F<./os2/diff.*> like this: - gnupatch -p0 < os2\POSIX.mkfifo gnupatch -p0 < os2\diff.configure You may also need to apply the patches supplied with the binary @@ -832,7 +830,7 @@ to EMX headers: +++ /emx/include/sys/stat.h Sun Jul 12 14:11:32 1998 @@ -53,7 +53,7 @@ struct stat #endif - + #if !defined (S_IFMT) -#define S_IFMT 0160000 /* Mask for file type */ +#define S_IFMT 0170000 /* Mask for file type */ @@ -1138,7 +1136,7 @@ Really really odious function to implement. Returns absolute name of file which would have C if CWD were C. C defaults to the current dir. -=item C Get current value of extended library search path. If C is present and I, works with END_LIBPATH, otherwise with @@ -1483,7 +1481,7 @@ this works as well under DOS if you use DOS-enabled port of pdksh B currently F of pdksh calls external programs via fork()/exec(), and there is I functioning exec() on -OS/2. exec() is emulated by EMX by asyncroneous call while the caller +OS/2. exec() is emulated by EMX by asynchronous call while the caller waits for child completion (to pretend that the C did not change). This means that 1 I copy of F is made active via fork()/exec(), which may lead to some resources taken from the system (even if we do @@ -1527,8 +1525,8 @@ as when processing B<-S> command-line switch. Perl uses its own malloc() under OS/2 - interpreters are usually malloc-bound for speed, but perl is not, since its malloc is lightning-fast. -Perl-memory-usage-tuned benchmarks show that Perl's malloc is 5 times quickier -than EMX one. I do not have convincing data about memory footpring, but +Perl-memory-usage-tuned benchmarks show that Perl's malloc is 5 times quicker +than EMX one. I do not have convincing data about memory footprint, but a (pretty random) benchmark showed that Perl one is 5% better. Combination of perl's malloc() and rigid DLL name resolution creates