
The patch to configure contains the following:

*** 3316,3322 ****
  fi
  rm -f conftest*
  
! if test x$ac_cv_prog_gcc = xyes; then
      echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
  echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then
--- 3316,3322 ----
  fi
  rm -f conftest*
  
! if test $ac_cv_prog_gcc = yes; then
      echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
  echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
  if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then


I am worried that this has undone the patch which was required to get 
configure to run properly with anything other than GCC. (I haven't
actually tried 6.3.1, but this change affects that area of the code and
doesn't look healthy...)


Andrew

----------------------------------------------------------------------------
Dr. Andrew C.R. Martin                             University College London
EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
URL:   http://www.biochem.ucl.ac.uk/~martin
Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775

Mon, 23 Mar 1998 17:43:41 GMT
Andrew Martin <martin@biochemistry.ucl.ac.uk>
URGENT PROBLEM with the 6.3->6.3.1 patch
Marc, can you comment on this.

> 
> 
> The patch to configure contains the following:
> 
> *** 3316,3322 ****
>   fi
>   rm -f conftest*
>   
> ! if test x$ac_cv_prog_gcc = xyes; then
>       echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
>   echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
>   if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then
> --- 3316,3322 ----
>   fi
>   rm -f conftest*
>   
> ! if test $ac_cv_prog_gcc = yes; then
>       echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
>   echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
>   if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then
> 
> 
> I am worried that this has undone the patch which was required to get 
> configure to run properly with anything other than GCC. (I haven't
> actually tried 6.3.1, but this change affects that area of the code and
> doesn't look healthy...)
> 
> 
> Andrew
> 
> ----------------------------------------------------------------------------
> Dr. Andrew C.R. Martin                             University College London
> EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
> URL:   http://www.biochem.ucl.ac.uk/~martin
> Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775
> 
> 


-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

Mon, 23 Mar 1998 12:54:52 -0500 (EST)
Bruce Momjian <maillist@candle.pha.pa.us>
Re: [HACKERS] URGENT PROBLEM with the 6.3->6.3.1 patch
On Mon, 23 Mar 1998, Bruce Momjian wrote:

> Marc, can you comment on this.

	It kind of bothers me that something that is standard in autoconf
breaks on some systems, while, as far as I can tell, its always been this
way ;(

	Andrew, have you asked the developers of autoconf about this?


> > The patch to configure contains the following:
> > 
> > *** 3316,3322 ****
> >   fi
> >   rm -f conftest*
> >   
> > ! if test x$ac_cv_prog_gcc = xyes; then
> >       echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
> >   echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
> >   if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then
> > --- 3316,3322 ----
> >   fi
> >   rm -f conftest*
> >   
> > ! if test $ac_cv_prog_gcc = yes; then
> >       echo $ac_n "checking whether ${CC-cc} needs -traditional""... $ac_c" 1>&6
> >   echo "configure:3322: checking whether ${CC-cc} needs -traditional" >&5
> >   if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set"; then
> > 
> > 
> > I am worried that this has undone the patch which was required to get 
> > configure to run properly with anything other than GCC. (I haven't
> > actually tried 6.3.1, but this change affects that area of the code and
> > doesn't look healthy...)
> > 
> > 
> > Andrew
> > 
> > ----------------------------------------------------------------------------
> > Dr. Andrew C.R. Martin                             University College London
> > EMAIL: (Work) martin@biochem.ucl.ac.uk    (Home) andrew@stagleys.demon.co.uk
> > URL:   http://www.biochem.ucl.ac.uk/~martin
> > Tel:   (Work) +44(0)171 419 3890                    (Home) +44(0)1372 275775
> > 
> > 
> 
> 
> -- 
> Bruce Momjian                          |  830 Blythe Avenue
> maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
>   +  If your life is a hard drive,     |  (610) 353-9879(w)
>   +  Christ can be your backup.        |  (610) 853-3000(h)
> 

Marc G. Fournier                                
Systems Administrator @ hub.org 
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org 


Mon, 23 Mar 1998 17:17:08 -0400 (AST)
The Hermit Hacker <scrappy@hub.org>
Re: [HACKERS] URGENT PROBLEM with the 6.3->6.3.1 patch