Path: utzoo!attcan!uunet!mcsun!hp4nl!tuegate.tue.nl!rcpt From: rcpt@tuegate.tue.nl (Piet Tutelaers) Newsgroups: comp.lang.perl Subject: Re: perl 3.0.18 for DECstation 3100? Message-ID: <1690@tuegate.tue.nl> Date: 14 Apr 90 17:51:15 GMT References: <1689@tuegate.tue.nl> Organization: Eindhoven University of Technology, The Netherlands Lines: 33 vixie@decwrl.dec.com (Paul A Vixie) writes: >>> I have problems in getting Perl3.0.18 running on our DECstation 3100. >A fellow Perl hacker here in corporate research told me recently that: > After running Config, if you change d_volatile to undef in config.sh > things seem to work. Thanks for this mental aid. I have undef-ed HASVOLATILE in config.h and after that all my problems mentioned before are over. Perhaps I can mention here too that to do optimization on DEC-MIPS machines one needs to increase the -Olimit, 3000 was a good value for me. To summarize, the value for CFLAGS on DEC-MIPS should be: CFLAGS = -DLANGUAGE_C -O -Olimit 3000 and the value of HASVOLATILE: /* HASVOLATILE: /*#undef HASVOLATILE /**/ I still get some warnings. I hope they will not give problems soon or later, so I will show one: -------------------------------------------------------------^ ccom: Warning: eval.c, line 1381: illegal pointer combination qhand = signal( 3 , ((void (*)())( 1))); -----------------------------------------------------^ I still have the problem that DEC (also on there newest DECstations) does not offer a version of ndbm, but only the old-fashioned dbm routines. These have the disadvantage that in one program only one databse can be opened. I know that there exist a GNU (beta) release of gdbm with a ndbm interface. The data base of gdbm is incompatible with BSD ndbm and dbm. Will perl use ever these gdbm routines? --Piet