This is what the output is from configure:
nyap_at_aviiondevelop:~/proj/oss/fvwm-2.2> ./configure
creating cache ./config.cache
checking for a BSD compatible install... ./install-sh -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... missing
checking for working autoconf... missing
checking for working automake... missing
checking for working autoheader... missing
checking for working makeinfo... found
checking whether to enable modal dialogs for applications... yes
checking whether to enable saveunders for pop-up menus... yes
checking whether to enable shape extensions... yes
checking whether to enable ActiveDown button state... yes
checking whether to enable Inactive button state... yes
checking whether to enable MiniIcon style option... yes
checking whether to enable vector button style... yes
checking whether to enable pixmap button style... yes
checking whether to enable gradient button style... yes
checking whether to enable stacked button styles... yes
checking whether to enable styled title-bars... yes
checking whether to enable BorderStyle command... yes
checking whether to enable UseDecor style option... yes
checking whether to enable WindowShade function... yes
checking whether to enable debugging messages... no
checking iconpath... /usr/include/X11/bitmaps:/usr/include/X11/pixmaps
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
checking how to run the C preprocessor... gcc -E
checking for POSIXized ISC... no
checking for minix/config.h... no
checking for stdarg.h... yes
checking for vfprintf... yes
checking for waitpid... yes
checking for c++... no
checking for g++... g++
Using g++ to compile C++ programs
checking for c++... (cached) g++
checking whether the C++ compiler (g++ ) works... no
configure: error: installation or configuration problem: C++ compiler cannot create
executables.
Here are the contents of config.log:
nyap_at_aviiondevelop:~/proj/oss/fvwm-2.2> cat config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:610: checking for a BSD compatible install
configure:663: checking whether build environment is sane
configure:720: checking whether make sets ${MAKE}
configure:766: checking for working aclocal
configure:779: checking for working autoconf
configure:792: checking for working automake
configure:805: checking for working autoheader
configure:818: checking for working makeinfo
configure:853: checking whether to enable modal dialogs for applications
configure:874: checking whether to enable saveunders for pop-up menus
configure:895: checking whether to enable shape extensions
configure:919: checking whether to enable ActiveDown button state
configure:943: checking whether to enable Inactive button state
configure:967: checking whether to enable MiniIcon style option
configure:991: checking whether to enable vector button style
configure:1015: checking whether to enable pixmap button style
configure:1039: checking whether to enable gradient button style
configure:1063: checking whether to enable stacked button styles
configure:1087: checking whether to enable styled title-bars
configure:1111: checking whether to enable BorderStyle command
configure:1135: checking whether to enable UseDecor style option
configure:1159: checking whether to enable WindowShade function
configure:1183: checking whether to enable debugging messages
configure:1204: checking iconpath
configure:1231: checking for gcc
configure:1344: checking whether the C compiler (gcc ) works
configure:1360: gcc -o conftest conftest.c 1>&5
configure:1386: checking whether the C compiler (gcc ) is a cross-compiler
configure:1391: checking whether we are using GNU C
configure:1400: gcc -E conftest.c
configure:1419: checking whether gcc accepts -g
configure:1451: checking how to run the C preprocessor
configure:1472: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1532: checking for POSIXized ISC
configure:1554: checking for minix/config.h
configure:1564: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1560: minix/config.h: No such file or directory
configure: failed program was:
#line 1559 "configure"
#include "confdefs.h"
#include <minix/config.h>
configure:1607: checking for stdarg.h
configure:1617: gcc -E conftest.c >/dev/null 2>conftest.out
configure:1646: checking for vfprintf
configure:1674: gcc -o conftest -g -O2 conftest.c 1>&5
configure:1706: checking for waitpid
configure:1734: gcc -o conftest -g -O2 conftest.c 1>&5
configure:1873: checking for c++
configure:1873: checking for g++
configure:1911: checking for c++
configure:1943: checking whether the C++ compiler (g++ ) works
configure:1959: g++ -o conftest conftest.C 1>&5
ld: /usr/lib/gcc-2/gcc-gnulib: fatal error: cannot open file for reading
configure: failed program was:
#line 1954 "configure"
#include "confdefs.h"
int main(){return(0);}
"Paul D. Smith" wrote:
> %% Noel Yap <nyap_at_garban.com> writes:
>
> ny> Then the configure script should be fixed. On my machines, if a
> ny> non-viable C++ compiler (ie possibly an old compiler) is found,
> ny> the configure fails with an error.
>
> Ouch!! Did this get reported before, and we just let it slip through
> the cracks?
>
> I don't see any Jitterbug report about it, but I would have lobbied hard
> to get it fixed before 2.2 if I'd known about it.
>
> Can you provide an example of what configure generates if you have a
> "non-viable" C++ compiler, and the appropriate contents of the
> config.log file?
>
> --
> -------------------------------------------------------------------------------
> Paul D. Smith <psmith_at_baynetworks.com> Network Management Development
> "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
> -------------------------------------------------------------------------------
> These are my opinions---Nortel Networks takes no responsibility for them.
> --
> Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
> To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
> message to majordomo_at_hpc.uh.edu.
> To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
--
Visit the official FVWM web page at <URL: http://fvwm.math.uh.edu/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Tue Feb 23 1999 - 10:14:57 GMT