From: Spider Boardman Date: Sat, 22 Feb 1997 09:51:48 +0000 (-0500) Subject: Ultrix hints X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=3a9ed036e1b1bbb39787aa3f3137a84abb977ce1;p=p5sagit%2Fp5-mst-13.2.git Ultrix hints Subject: Re: Perl 5.003_28 is available The hint file for ULTRIX is out of date with respect to the size of the Perl_yylex() function. I found this after enabling -O2, which works in recent versions of the compiler. Also, despite the inability of the standard dist unit to detect the fact, the ULTRIX dirent struct does too have a d_namelen field. Patch for that attached. Also, of course, as expected, ULTRIX still fails t/io/fs.t test #25, since [f]truncate can't be used to extend a file on that OS. All other tests are fine. p5p-msgid: <199702220951.EAA08156@Orb.Nashua.NH.US> --- diff --git a/hints/ultrix_4.sh b/hints/ultrix_4.sh index 826cb34..d3c4a39 100644 --- a/hints/ultrix_4.sh +++ b/hints/ultrix_4.sh @@ -6,7 +6,13 @@ # # This used to use -g, but that pulls in -DDEBUGGING by default. case "$optimize" in -'') optimize='none' ;; +'') + # recent versions have a working compiler. + case "$osvers" in + *4.[45]*) optimize='-O2' ;; + *) optimize='none' ;; + esac + ;; esac # Some users have reported Configure runs *much* faster if you @@ -28,16 +34,16 @@ case "$cc" in *gcc*) ;; *) case "$osvers" in - *4.1*) ccflags="$ccflags -DLANGUAGE_C -Olimit 2900" ;; - *4.2*) ccflags="$ccflags -DLANGUAGE_C -Olimit 2900" + *4.1*) ccflags="$ccflags -DLANGUAGE_C -Olimit 3200" ;; + *4.2*) ccflags="$ccflags -DLANGUAGE_C -Olimit 3200" # Prototypes sometimes cause compilation errors in 4.2. prototype=undef case "$myuname" in *risc*) d_volatile=undef ;; esac ;; - *4.3*) ccflags="$ccflags -std1 -DLANGUAGE_C -Olimit 2900" ;; - *) ccflags="$ccflags -std -Olimit 2900" ;; + *4.3*) ccflags="$ccflags -std1 -DLANGUAGE_C -Olimit 3200" ;; + *) ccflags="$ccflags -std -Olimit 3200" ;; esac ;; esac @@ -54,3 +60,7 @@ esac util_cflags='ccflags="$ccflags -DLOCALE_ENVIRON_REQUIRED"' groupstype='int' +# This will cause a WHOA THERE warning, but it's accurate. The +# configure test should be beefed up to try using the field when +# it can't find any of the standardly-named fields. +d_dirnamlen='define'