You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by ma...@hyperreal.org on 2000/01/10 11:39:52 UTC

cvs commit: apache-1.3/src Configure

martin      00/01/10 02:39:51

  Modified:    src      Configure
  Log:
  Improve compilation on RISC-based BS2000 mainframes by autodetecting the
  presence of MIPS CPUs (speed improvement 3..6-fold)
  
  Revision  Changes    Path
  1.384     +6 -0      apache-1.3/src/Configure
  
  Index: Configure
  ===================================================================
  RCS file: /export/home/cvs/apache-1.3/src/Configure,v
  retrieving revision 1.383
  retrieving revision 1.384
  diff -u -r1.383 -r1.384
  --- Configure	1999/12/20 14:50:55	1.383
  +++ Configure	2000/01/10 10:39:46	1.384
  @@ -1484,6 +1484,12 @@
   	fi
   	;;
       BS2000*-siemens-sysv4*)
  +	# Activate RISC compilation if this is a SR2000 machine
  +	# (test written by Thomas Dorner <Th...@start.de>
  +	# for perl5 port):
  +	if [ -n "`bs2cmd SHOW-SYSTEM-INFO | grep 'HSI-ATT.*TYPE.*SR'`" ]; then
  +	    CFLAGS="$CFLAGS -Krisc_4000"
  +	fi
   	# Depending on the BS2000 OS and compiler/crte release,
   	# -lnsl may be available (or may be not).
   	# In standard SVR4 systems, -lsocket relies on some symbols
  
  
  

Re: cvs commit: apache-1.3/src Configure

Posted by Martin Kraemer <Ma...@Mch.SNI.De>.
On Mon, Jan 10, 2000 at 07:30:43AM -0500, Jim Jagielski wrote:
> I don't think we use this construct anyplace else... Being so
> close to 1.3.10, this makes me a little nervous :)

It's alright (this branch is really only executed on BS2000).

> Is it OK if I switch that to:
> 
> 	ISSR2000="`bs2cmd SHOW-SYSTEM-INFO | grep 'HSI-ATT.*TYPE.*SR'`"
> 	case "$ISSR2000" in
> 	   *HSI-ATT.*TYPE.*SR*)
> 	      CFLAGS="$CFLAGS -Krisc_4000"
> 	      ;;
> 	esac

Yes, would be fine with me just as well. I simply copied over the other
"if" from perl and did not think of the test [ -n ... ], sorry.

> PS: Not sure what the output is of bs2cmd SHOW-SYSTEM-INFO but we
>     could drop that grep as well I'm thinking, unless it's multi-line
>     in which case the grep kinda makes sense.

Yes, it's about 20 lines.
But: good point (I dislike the heavy use of grep too).

Change as you feel fit. But to the best of my knowledge ;-) this shouldn't
have hurt any other platform.

    Martin
-- 
  <Ma...@MchP.Siemens.De>      |       Fujitsu Siemens
       <ma...@apache.org>              |   81730  Munich,  Germany