On Tue, 16 Oct 2001, Sabyasachi Gupta wrote:
> [....]
> configure:526: checking for gcc
> configure:603: checking whether the C compiler (gcc ) works
> configure:617: gcc -o conftest conftest.c 1>&5
> gcc: installation problem, cannot exec `cpp0': No such file or directory
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Well, that's pretty specific. Have you checked that there is a file
called 'cpp0'? If not, then why not? Else: Is it in a path where your
install process can find it? (How do you "know"--on what basis have you
determined--that it is found?) Does it have "execute" permissions? Have
you tried calling it up?
> configure: failed program was:
> #line 613 "configure"
> #include "confdefs.h"
Likewise: have you checked that 'confdefs.h' actually exists?
These kinds of messages are all clues. They may be incomplete,
irrelevant, or even misleading, but they all have some kind of
significance. (I.e., they each are there for some reason.) The first
step of debugging is to _examine the error messages_!, and consider what
they are trying to tell you.
=== JJ =============================================================
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
