Xref: utzoo comp.lang.perl:5058 comp.sys.apollo:8856
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!sun-barr!newstop!sun!amdcad!brahms!dwork
From: dwork@brahms.amd.com (Jeff Dwork)
Newsgroups: comp.lang.perl,comp.sys.apollo
Subject: Re: Strange error compiling Perl 4.03 on Apollo (cc 6.8, SR10.3)
Message-ID: <1991Apr24.205645.22218@amd.com>
Date: 24 Apr 91 20:56:45 GMT
References: <heffron.672442769@falstaff.css.beckman.com>
Sender: usenet@amd.com (NNTP Posting)
Organization: Advanced Micro Devices; Sunnyvale, CA
Lines: 74

In article <heffron.672442769@falstaff.css.beckman.com> heffron@falstaff.css.beckman.com writes:
>I've gotten a really strange error trying to compile cmd.c from the Perl 4.03
>distribution, using the cc 6.8 on a dn3500 running SR10.3, systype=BSD4.3 :
>
>/bin/cc -c `sh cflags.SH cmd.o` cmd.c
>	  CFLAGS =  -A cpu,mathchip
>
> (0044) {
>
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(READ)" is inappropriate in this
>         context.
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(WRITE)" is inappropriate in this
>         context.
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(READ)" is inappropriate in this
>         context.
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(WRITE)" is inappropriate in this
>         context.
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(READ)" is inappropriate in this
>         context.
>******** Line 44 of "cmd.c": [Warning #233]  "DEVICE(WRITE)" is inappropriate in this
>         context.
>
>The context around line 44 is:
>
>int
>cmd_exec(cmdparm,gimme,sp)
>CMD *VOLATILE cmdparm;
>VOLATILE int gimme;
>VOLATILE int sp;
>{
>    register CMD *cmd = cmdparm;
>    SPAT *VOLATILE oldspat;
>    VOLATILE int firstsave = savestack->ary_fill;
>    VOLATILE int oldsave;
>    VOLATILE int aryoptsave;
>
>
>The macro "VOLATILE" expands as "volatile" (w/o the quotes).
>
>Any clues?
>
>If this is a legitimate warning, then THE WARNING MESSAGE TEXT COULD (SHOULD!!)
>BE A WHOLE LOT MORE SPECIFIC!!!!!!!!!!!
>
>-Matt
>
>PS. the Configure script computes the "void" support level to be 3 when it
>should be 7.  This is because it invokes the compile of the test program with
>the -S option which Apollo doesn't support.  Likewise, it determines that malloc
>returns type "char *" instead of "void *" because the test program #includes
><malloc.h> which doesn't exist on Apollo.
>
>--
>Matt Heffron                      heffron@falstaff.css.beckman.com
>Beckman Instruments, Inc.         voice: (714) 961-3128
>2500 N. Harbor Blvd. MS X-11, Fullerton, CA 92634-3100
>Cute saying/disclaimer in development.


I compiled perl with version 6.7 of cc, SR 10.3, systype bsd4.3 on HP400t.
CFLAGS='-A nansi cpu,mathchip -O'.  I told config that void support was 7.
(I hope that's right).  Everything works ok except for some warnings about
illegal pointer combinations (I don't remember this from 3.044).

Everything passes except for io/fs test 5 and op/dbm test 2, both of which
have to do with 'mode' returned by 'stat'.  Don't have time to look at this
now.

--Jeff
--
Jeff Dwork			|  408-749-2356 	|  dwork@AMD.COM
Advanced Micro Devices, M/S 45	|---------------------------------------
PO Box 3453			|  The above opionions are mine,
Sunnyvale, Ca 94088		|  not AMD's.