Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!samsung!sol.ctr.columbia.edu!caen!ox.com!hela!widener!ukma!eng.ufl.edu!math.ufl.edu!uflorida!mlb.semi.harris.com!rtpark.rtp.semi.harris.com!mcnc!rti!mozart!sherman From: sherman@unx.sas.com (Chris Sherman) Newsgroups: comp.lang.perl Subject: Compiling perl on IRIX3.3. Message-ID: Date: 4 Jun 91 23:42:35 GMT Sender: news@unx.sas.com (Noter of Newsworthy Events) Distribution: sas Organization: SAS Institute Inc. Lines: 47 Nntp-Posting-Host: foster.unx.sas.com I just finished compiling perl on an IRIS, 3.3. For anyone else who has had problems, I offer these tips for perl version 4 patch 3 ... Add -D_BSD_COMPAT to the compiler options in Configure. In config.sh, set the following variables to 'undef', d_volatile='undef' d_memcmp='undef' d_vfork='undef' The program compiles (kind of, see below), but fails two tests: comp/decl......FAILED on test 7 op/write.......FAILED on test 1 I was getting unusual errors from the compiler, but not serious enough for the compiler to stop. The following is typical of the errors I was getting: cc -c -DTAINT `sh cflags.SH ttoke.o` ttoke.c CFLAGS = -Uf_next -I/usr/include/sun -I/usr/include/bsd -D_BSD_COMPATccom: Warning: ttoke.c, line 2333: illegal member use: f_up return froot. f_up.f_unext; -----------------------------^ Note the original line in the file is: return froot.f_next; In , f_next was defined to be f_up.f_unext, which I guess was bad, because I did the following fix, and the problem went away. Edit toke.c, and add the following line after all the other include statements: #undef f_next Now, All tests successful. u=0.63 s=1.9 cu=4.22 cs=6.15 Hope this helps, -- Chris Sherman .................... sherman@unx.sas.com | ,-----------------------------------------' / Q: How many IBM CPU's does it take to execute a job? | A: Four; three to hold it down, and one to rip its head off.