./configure no compiler found error

[darkangelx]

checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking whether make sets $(MAKE)... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for g++... g++
checking for supported compiler version... checking for C++ compiler default output... configure: error: C++ compiler cannot create executables
See `config.log' for more details.


attached is my logfile

I tried to update gcc and g++ with slackware packages (if anyone is familiar with it) Well before I was having problem compiling QT, but i think i screwed my compiler all together.


Advice if able...

[Cryonic]

I don't know about you, but these two lines:

x_includes='NONE'
x_libraries='NONE'

seem kind of suspicious to me.

[darkangelx]

what does that have to do with my compiler? X isnt even involved at this point unless x_include is something I dont know about...

[darkangelx]

as far as I can tell this is most relivent part of the config.log file:



configure:1885: checking for gcc
configure:1901: found /usr/local/bin/gcc
configure:1911: result: gcc
configure:1925: checking for g++
configure:1941: found /usr/local/bin/g++
configure:1951: result: g++
configure:1984: checking for supported compiler version
configure:2086: checking for C++ compiler version
configure:2089: g++ --version </dev/null >&5
g++ (GCC) 3.2.3
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

configure:2092: $? = 0
configure:2094: g++ -v </dev/null >&5
Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-_
_cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackw
are-linux
Thread model: posix
gcc version 3.2.3
configure:2097: $? = 0
configure:2099: g++ -V </dev/null >&5
g++: argument to `-V' missing

configure:2102: $? = 1
configure:2126: checking for C++ compiler default output
configure:2129: g++ conftest.cc >&5
/usr/bin/ld: unrecognized option '--eh-frame-hdr'
/usr/bin/ld: use the --help option for usage information
collect2: ld returned 1 exit status
configure:2132: $? = 1
configure: failed program was:
| #line 2105 "configure"
| /* confdefs.h. */

[Cryonic]

nm, guess those are set to NONE since it hasn't gotten around to checking for them. Another oddity that I see in the log:

configure:1885: checking for gcc
configure:1901: found /usr/local/bin/gcc
configure:1911: result: gcc
configure:1925: checking for g++
configure:1941: found /usr/local/bin/g++
configure:1951: result: g++

yet when it goes to check the environment for them

Reading specs from /usr/lib/gcc-lib/i486-slackware-linux/3.2.3/specs
Configured with: ../gcc-3.2.3/configure --prefix=/usr --enable-shared --enable-threads=posix --enable-__cxa_atexit --disable-checking --with-gnu-ld --verbose --target=i486-slackware-linux --host=i486-slackware-linux

So, why is it finding gcc in /usr/local/bin when gcc-3.2.3 was compiled with --prefix=/usr which should have dumped it in /usr/bin

On most other systems (RH, Debian, Mandrake, etc...) a compiler that can't make executeables is due to a lack of the glibc-devel files.

[darkangelx]

interesting... ill look into it... however as long as the finds the files it needs should it really matter where it is located?

[darkangelx]

problem solved...
binutils-2.14.90.0.6-i486-1.tgz

required for compiling, installed the package and its fixed. Thanks for your assistance.. back to the QT problem now heh