C compiler cannot create executables

70mas · 09-30-2006, 01:01 PM

I am trying to compile Apache 2.2.3 on a Slackware 10.2 OS. When I start ./configure, I get this:

Quote:

root@slack:~/httpd-2.2.3# ./configure
checking for chosen layout... Apache
checking for working mkdir -p... yes
checking build system type... i686-pc-linux-gnulibc1
checking host system type... i686-pc-linux-gnulibc1
checking target system type... i686-pc-linux-gnulibc1

Configuring Apache Portable Runtime library ...

checking for APR... reconfig
configuring package in srclib/apr now
checking build system type... i686-pc-linux-gnulibc1
checking host system type... i686-pc-linux-gnulibc1
checking target system type... i686-pc-linux-gnulibc1
Configuring APR library
Platform: i686-pc-linux-gnulibc1
checking for working mkdir -p... yes
APR Version: 1.2.7
checking for chosen layout... apr
checking for gcc... gcc
checking for C compiler default output file name... configure: error: C compiler cannot create executables
See `config.log' for more details.
configure failed for srclib/apr

I think that this issue is very usual but is nowhere documented how to solve this... If you can, please help me. I have been fighting with this already for 4 hours. I found out that kernel-headers and glibc-devel packages have to be installed. I reinstalled my linux machine, I installed the kernel-headers package, but I didnt find glibc-devel anywhere...

Your help would be very appreciated. Thanks.

crazyjimbo · 09-30-2006, 02:16 PM

Have you looked at config.log for details? You probably don't have one of the many programs gcc uses to make the final executable (ln, etc).

BiThian · 09-30-2006, 03:44 PM

Quote:

Originally Posted by 70mas

I reinstalled my linux machine, I installed the kernel-headers package, but I didnt find glibc-devel anywhere...

If you meant to say "I reinstalled linux on my machine", I have to tell you that Linux != Windows

PS: Sorry for the off-topic

centralb · 01-02-2007, 12:54 AM

In some situations, it can help to remove any preceding CPPFLAGS or LDFLAGS initializations on the same line as the ./configure command.

As an alternative, set and export them in separate statements prior to the ./configure command (taking care if you need to use different values for other installs). Using LIBS and INCLUDES in this manner seems to be more reliable than setting CPPFLAGS and LDFLAGS to reference "non-standard" includes and libs for Apache 2.