Thread

  1. configure doesn't handle --with-compiler correctly

    Pedro J. Lobo <pjlobo@euitt.upm.es> — 1998-02-16T12:02:06Z

    Hi, all.
    
    I have compiled the Feb. 15 snapshot on a DEC alpha and, besides other
    problems that I've reported in the psql-ports list, there is a bug in
    configure that has been there for quite a while.
    
    I use this command to do the 'configure' thing:
    
    ./configure --prefix=/usr/local/pgsql.beta --enable-locale
    --with-pgport=5440 --enable-cassert --with-compiler=cc
    
    I use --with-compiler=cc because I have both DEC C ang GNU gcc installed,
    and I've found DEC C to generate better code (faster) than gcc.
    
    The problem is that when the configure script tries to figure out if we
    are using gcc, to check if it needs the -traditional flag, it dies (the
    script).
    
    This is the patch I use as a workaround:
    
    ----------------------------------------------------
    *** configure.orig      do 15 feb 09:00:37 1998
    --- configure   lu 16 feb 11:37:21 1998
    ***************
    *** 3224,3230 ****
      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:3230: checking whether ${CC-cc} needs -traditional" >&5
      if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set";
    then
    --- 3224,3230 ----
      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:3230: checking whether ${CC-cc} needs -traditional" >&5
      if eval "test \"`echo '$''{'ac_cv_prog_gcc_traditional'+set}'`\" = set";
    then
    -----------------------------------------------------------
    
    The problem is that $ac_cv_prog_gcc is empty, instead of 'no' or
    whatsoever. The patch is not a solution, because configure is generated
    from configure.in, and I don't know how to patch it to get a working
    'configure'.
    
    Is there any autoconf guru that has a solution? Marc?
    
    	Pedro.
    
    -------------------------------------------------------------------
    Pedro José Lobo Perea                   Tel:    +34 1 336 78 19
    Centro de Cálculo                       Fax:    +34 1 331 92 29
    EUIT Telecomunicación - UPM             e-mail: pjlobo@euitt.upm.es
    
    
    
  2. Re: [HACKERS] configure doesn't handle --with-compiler correctly

    Marc G. Fournier <scrappy@hub.org> — 1998-02-17T01:31:19Z

    On Mon, 16 Feb 1998, Pedro J. Lobo wrote:
    
    > The problem is that $ac_cv_prog_gcc is empty, instead of 'no' or
    > whatsoever. The patch is not a solution, because configure is generated
    > from configure.in, and I don't know how to patch it to get a working
    > 'configure'.
    > 
    > Is there any autoconf guru that has a solution? Marc?
    
    	The only solution that I have is to re-install autoconf after
    modifying the appropriate line in acspecific.m4 ... now every time I do an
    autoconf at this end, it will have the 'x's in front of the appropraite
    variables...
    
    Marc G. Fournier                                
    Systems Administrator @ hub.org 
    primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org