X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=README.beos;h=0a01f50b9ee0aee895e85d8f53a8eadc00f6da88;hb=62703e7218aceb3f5d30f70a2307dd02e5eb8c63;hp=ccd9cbc6c68edca5b06b3278efd3da16b06554a0;hpb=4619340914cc8b5438e9411eca00b9f6a4805995;p=p5sagit%2Fp5-mst-13.2.git diff --git a/README.beos b/README.beos index ccd9cbc..0a01f50 100644 --- a/README.beos +++ b/README.beos @@ -1,43 +1,109 @@ -Notes on building perl under BeOS: +If you read this file _as_is_, just ignore the funny characters you see. +It is written in the POD format (see pod/perlpod.pod) which is specially +designed to be readable as is. -GENERAL ISSUES --------------- -how to compile perl: +=head1 NAME -To compile perl under BeOS R4 x86: +README.beos - Perl version 5.8+ on BeOS -`./Configure -d` and hit ^C when it asks you if you want to make changes -to config.sh; +=head1 DESCRIPTION -edit config.sh and do the following: -change d_socket='define' to ='undef'; -remove SDBM, Errno, and Socket from dynamic_ext= and nonxs_ext=; +This file contains instructions how to build Perl under BeOS and lists +known problems. -add '#define bool short' to x2p/a2p.h; +=head1 BUILD AND INSTALL -../Configure -S; make; make install +=head2 Requirements -cd ~/config/lib; ln -s 5.00502/BeOS-BePC/CORE/libperl.so . -(substitute 5.00502 with the appropriate filename) +I have built and tested Perl 5.8.6 and 5.9.1 under BeOS R5 x86 net server. +I can't say anything with regard to PPC. Since Perl 5.8.0 had been released +for BeOS BONE, I suspect, there is a good chance, that it still compiles on +a BONE system. The only change I've made, that affects BONE systems is the +recognition of whether it is a BONE system or not in C. Now +network socket support should remain enabled on BONE systems. This might +as well break the build, though. -OS RELEASE-SPECIFIC NOTES -------------------------- -R4 x86 - dynamic loading finally works! Yay! This means you can compile -your own modules into perl. However, Sockets and Errno still don't work. -(Hopefully, sockets will at least work by R5, if not sooner.) +As more recent versions of autoconf require flock() support, I wrote a flock() +emulation (flock_server) and released it on BeBits: -R4 PPC - I have not tested this. I rather severely doubt that dynamic -loading will work. (My BeBox is in pieces right now, following a nasty -disk crash.) You may have to disable dynamic loading to get the thing -to compile at all. (use `./Configure` without -d, and say 'no' to -'Build a shared libperl.so'.) + http://www.bebits.com/app/4030 -CONTACT INFORMATION -------------------- -If you have comments, problem reports, or even patches or bugfixes (gasp!) -please email me. +If you want to build a Perl with flock() support, you have to install this +package first. -28 Jan 1999 -Tom Spindler -dogcow@isi.net +=head2 Configure +With flock() support: + + CFLAGS=-I/path/to/flock/server/headers ./configure.gnu \ + --prefix=/boot/home/config + +Replace C with the path to the directory +containing the C header. + +Without flock() support: + + ./configure.gnu --prefix=/boot/home/config + +=head2 Build + +With flock() support: + + make LDLOADLIBS="-lnet -lflock" + +Without flock() support: + + make LDLOADLIBS="-lnet" + +C<-lnet> is needed on net server systems only and if the compiler doesn't +add it automatically (Be's R5 gcc does, Oliver Tappe's gcc 2.95.3 does not). + +=head2 Install + +Install all perl files: + + make install + +Create a symlink for libperl: + + cd ~/config/lib; ln -s perl5/5.8.6/BePC-beos/CORE/libperl.so . + +Replace C<5.8.6> with your respective version of Perl. + +=head1 KNOWN PROBLEMS + +=over 4 + +=item * + +Network socket support is disabled for BeOS R5 net server. I didn't dare yet +to try enabling it and see what problems occur. + +=item * + +The LFS (large file support) tests (C and C) are +disabled as seeking beyond 2 GB is broken according to jhi@iki.fi who was the +last one checking the BeOS port and updating this file before me. Haven't +checked this myself. + +=item * + +The C test fails at #6. As far as I can tell, this is caused by +a bug in the BeOS pipes implementation that occurs when starting other child +processes. In the particular test case a C flushes the +stdout pipe of another child process. + +=item * + +The C test fails at #1. After all child processes are +gone BeOS' waitpid(-1,...) returns 0 instead of -1 (as it should). No idea +how to fix this. + +=back + +=head1 CONTACT + +For BeOS specifics problems feel free to mail to: +Ingo Weinhold + +Last update: 2004-12-16