Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!uunet!mcsun!hp4nl!mhres!squirrel!pronto!jv From: jv@mh.nl (Johan Vromans) Newsgroups: comp.lang.perl Subject: Perl 4.0 pl 9 on Ultrix 4.0 Message-ID: <1991Jun10.140504.4424@pronto.mh.nl> Date: 10 Jun 91 14:05:04 GMT Sender: jv@pronto.mh.nl (Johan Vromans) Reply-To: Johan Vromans Distribution: comp Organization: Multihouse Automation, the Netherlands Lines: 30 X-Md4-Signature: 4cf9266ab0b8e65a33ac6429f20a7996 DecSystem5000 (Ultrix/RISC 4.0) with GCC 1.39 (OSF #3). 1. Strange things happens when the 'new' Configure tries to digest the 'old' config.sh file. The 'old' config.sh (pl3) file contained a value for the variable 'tmp', that conflicts (see the processing of config.sh in Configure). The newly generated config.sh and friends seem ok, although the setting for tmp is propagated in the new config.sh. 2. A subsequent run of Configure -d refuses to process config.sh since it has decided that it was not produced on the same system. 3. In perl.h, '#undef HAS_MEMCMP' needs to be commented out at line 105. Otherwise 'util.c' won't compile due to prototype mismatch. 4. Tests io/dup and io/pipe fail. For some reason, io/dup needs $^F >= 5 and io/pipe needs $^F >= 4. 5. The Configure question "Are your system (especially dbm) libraries compiled with gcc" is misleading. Better is: "Does gcc has to use '-fpcc-struct-return' to avoid conflicts with system libraries, especially dbm (Confirm if in doubt)" or something like that. Johan -- Johan Vromans jv@mh.nl via internet backbones Multihouse Automatisering bv uucp: ..!{uunet,hp4nl}!mh.nl!jv Doesburgweg 7, 2803 PL Gouda, The Netherlands phone/fax: +31 1820 62911/62500 ------------------------ "Arms are made for hugging" -------------------------