PATCH: Have gcc_build record CVS update as well

Mark Mitchell mark@codesourcery.com
Sun Oct 29 15:06:00 GMT 2000


I missed a spot where gcc_build should record output in the logfile --
during CVS update.

--
Mark Mitchell                   mark@codesourcery.com
CodeSourcery, LLC               http://www.codesourcery.com

2000-10-29  Mark Mitchell  <mark@codesourcery.com>

	* gcc_build: Save the output from CVS into the logfile as well.

Index: gcc_build
===================================================================
RCS file: /cvs/gcc/egcs/contrib/gcc_build,v
retrieving revision 1.4
diff -c -p -r1.4 gcc_build
*** gcc_build	2000/10/26 01:18:12	1.4
--- gcc_build	2000/10/29 23:04:02
*************** update_gcc() {
*** 118,124 ****
      changedir ${DESTINATION}
  
      # Update the tree
!     ./contrib/gcc_update || \
  	error "Could not update GCC"
  }
  
--- 118,124 ----
      changedir ${DESTINATION}
  
      # Update the tree
!     (./contrib/gcc_update | tee -a ${LOGFILE}) || \
  	error "Could not update GCC"
  }
  
*************** build_gcc() {
*** 139,150 ****
      # Configure the tree.
      (eval ${DESTINATION}/configure ${CONFIGURE_OPTIONS} | 
          tee -a ${LOGFILE}) 2>&1 || \
! 	error "Could not configure the compiler"
  
      # Bootstrap the compiler
      (eval make ${MAKE_OPTIONS} bootstrap |
  	tee -a ${LOGFILE}) 2>&1 || \
! 	error "Could not build the compiler"
  }
  
  # Test GCC.
--- 139,150 ----
      # Configure the tree.
      (eval ${DESTINATION}/configure ${CONFIGURE_OPTIONS} | 
          tee -a ${LOGFILE}) 2>&1 || \
! 	error "Could not configure GCC"
  
      # Bootstrap the compiler
      (eval make ${MAKE_OPTIONS} bootstrap |
  	tee -a ${LOGFILE}) 2>&1 || \
! 	error "Could not build GCC"
  }
  
  # Test GCC.


More information about the Gcc-patches mailing list