Hello. I have been trying to figure out why libtool tries to detect and use both gcc and cc. If anyone could provide some insight that would be great. Here is the output I am seeing while running ./configure ./configure ... checking for gcc... gcc checking whether the C compiler works... yes checking whether we are using GNU C... yes ... creating libtool updating cache /dev/null loading cache /dev/null within ltconfig checking host system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking for objdir... .libs checking for cc option to produce PIC... -fPIC checking if cc PIC flag -fPIC works... no ... checking whether to build shared libraries... no checking whether to build static libraries... yes appending configuration tag "GCJ" to libtool checking for gcc... (cached) gcc checking whether the C compiler works... yes ... Note how it picks up cc after it had already found gcc in a higher level directory. The main problem here is that when this build script is run under Cygwin it fails rather badly because no cc can be found (only gcc is on the PATH). Mo DeJong Red Hat Inc
