Thread

1. configure CXX bug

   Mark Hollomon <mhh@nortelnetworks.com> — 2000-08-18T15:00:22Z

   configure seems to be having a problem with --without-CXX
   When given, the C++ compiler is set to 'no'.
   
   This was with CVS as of about 10:00 EDT
   
   platform is linux i386 running Debian 'woody'.
    
    --- commandline ---
    
    ./configure --enable-debug --enable-cassert --enable-depend --without-python --without-perl --without-CXX
    
    --- OUTPUT ----
    
    creating cache ./config.cache
    checking host system type... i586-pc-linux-gnu
    checking which template to use... linux
    checking whether to build with locale support... no
    checking whether to build with Cyrillic recode support... no
    checking whether to build with multibyte character support... no
    checking for default port number... 5432
    checking for default soft limit on number of connections... 32
    checking for gcc... gcc
    checking whether the C compiler (gcc  ) works... yes
    checking whether the C compiler (gcc  ) is a cross-compiler... no
    checking whether we are using GNU C... yes
    checking whether gcc accepts -g... yes
    using CFLAGS=-O2
    checking whether the C compiler (gcc -O2 ) works... yes
    checking whether the C compiler (gcc -O2 ) is a cross-compiler... no
    checking how to run the C preprocessor... gcc -E
    checking whether gcc needs -traditional... no
    checking setting debug compiler flag... yes
    checking setting USE_TCL... disabled
    checking whether to build Perl modules... no
    checking whether to build Python modules... no
    checking whether to build the ODBC driver... no
    checking setting ASSERT CHECKING... enabled
    checking whether to build C++ modules... yes
    checking for c++... no
    checking whether the C++ compiler (no  ) works... no
    configure: error: installation or configuration problem: C++ compiler cannot create executables.
    
    ------ config.log --------
    
    This file contains any messages produced by compilers while
    running configure, to aid debugging if configure makes a mistake.
    
    configure:619: checking host system type
    configure:642: checking which template to use
    configure:787: checking whether to build with locale support
    configure:809: checking whether to build with Cyrillic recode support
    configure:832: checking whether to build with multibyte character support
    configure:872: checking for default port number
    configure:901: checking for default soft limit on number of connections
    configure:939: checking for gcc
    configure:1052: checking whether the C compiler (gcc  ) works
    configure:1068: gcc -o conftest    conftest.c  1>&5
    configure:1094: checking whether the C compiler (gcc  ) is a cross-compiler
    configure:1099: checking whether we are using GNU C
    configure:1108: gcc -E conftest.c
    configure:1127: checking whether gcc accepts -g
    configure:1163: checking whether the C compiler (gcc -O2 ) works
    configure:1179: gcc -o conftest -O2   conftest.c  1>&5
    configure:1205: checking whether the C compiler (gcc -O2 ) is a cross-compiler
    configure:1210: checking how to run the C preprocessor
    configure:1231: gcc -E  conftest.c >/dev/null 2>conftest.out
    configure:1291: checking whether gcc needs -traditional
    configure:1374: checking setting debug compiler flag
    configure:1429: checking setting USE_TCL
    configure:1482: checking whether to build Perl modules
    configure:1499: checking whether to build Python modules
    configure:1759: checking whether to build the ODBC driver
    configure:1795: checking setting ASSERT CHECKING
    configure:1843: checking whether to build C++ modules
    configure:1857: checking for c++
    configure:1889: checking whether the C++ compiler (no  ) works
    configure:1905: no -o conftest    conftest.C  1>&5
    ./configure: no: command not found
    configure: failed program was:
    
    #line 1900 "configure"
    #include "confdefs.h"
    
    int main(){return(0);}
   
   -- 
   
   Mark Hollomon
   mhh@nortelnetworks.com
   
   

2. Re: configure CXX bug

   Tom Lane <tgl@sss.pgh.pa.us> — 2000-08-19T05:39:04Z

   "Mark Hollomon" <mhh@nortelnetworks.com> writes:
   > configure seems to be having a problem with --without-CXX
   > When given, the C++ compiler is set to 'no'.
   
   > This was with CVS as of about 10:00 EDT
   
   Peter E. has been hacking the configure stuff since 7.0.  The behavior
   is now more consistent with GNU/autoconf standard practice, but not 100%
   backwards compatible.  I think that --without-CXX is now the default,
   and you need to say --with-CXX [=compiler] if you want the C++ code
   built.
   
   			regards, tom lane
   
   

3. Re: configure CXX bug

   Peter Eisentraut <peter_e@gmx.net> — 2000-08-19T23:42:22Z

   Mark Hollomon writes:
   
   > configure seems to be having a problem with --without-CXX
   > When given, the C++ compiler is set to 'no'.
   
   Fixed. Thanks.
   
   
   -- 
   Peter Eisentraut                  Sernanders väg 10:115
   peter_e@gmx.net                   75262 Uppsala
   http://yi.org/peter-e/            Sweden