Compiler Issues running ./configure

Khue · 08-26-2008, 04:14 PM

Hey everyone, I am having a problem dealing with an install (or 10).

I have a trimmed down version of Slackware (ver 10.2). It is a VMware appliance for running a Jabber server. While messing around with the Jabber server, I noticed that it didn't come with the ability to group chat so in order to do so, Jabber needed to be supplemented with mu-conference and mu-conference needed glib-2.0 or greater for the make file to run. I downloaded this package (glib-2.16.5.tar.gz) and got it on to the appliance I attempted to run

Code:

./configure

and I got the following error

Code:

configure: error: no acceptable C compiler found in $PATH

Browsing around I found that I needed to install gcc. I browsed the slackware package webpage and got gcc-g++-4.2.3-i486-1.tgz. I ftp'd the file to the /tmp folder and then ran:

Code:

installpkg gcc-g++-4.2.3-i486-1.tgz

Some stuff then happened and it appeared like it may have been installed correctly. I then attempted to run the configure command again and the output I received was as follows:

Code:

root@jabber:/tmp/glib-2.16.5# ./configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... i686-pc-linux-gnuoldld
checking host system type... i686-pc-linux-gnuoldld
checking for the BeOS... no
checking for Win32... no
checking for Mac OS X Carbon support... checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cl.exe... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

Config.log doesn't contain much more then what I posted above. Seemingly Slack doesn't know what the compiler is still. Can anyone help me troubleshoot a bit?

Thanks in advance.

Fidori · 08-26-2008, 04:26 PM

Do you have the gcc-4.2.3-i486-1 package installed?

Khue · 08-27-2008, 06:34 AM

Thanks Fidori, that got me a little farther. I am now erroring out with the following message:

Code:

checking for style of include used by make... GNU
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.

Output from the config.log file can be found here (clicky!).

jong357 · 08-27-2008, 08:13 AM

It's not finding the assembler (/usr/bin/as). Install binutils.

Wow. Slackware without gcc and binutils. Hard to imagine.

Road_map · 08-27-2008, 08:21 AM

I think he need gcc-g++-4.2.3-i486-1 package too.

jong357 · 08-27-2008, 08:23 AM

Also, I think your going about this all wrong.

First, your using Slackware 10.2 and trying to install the latest packages from 12.1 or current. It may or may not work when it's all said and done but I guess you'll find out soon enough.

What you should first try is selecting 10.2 from the drop down box when looking for packages. If you were to get an error later on stating that some prog is too old, then you should try upgrading. 10.2 does come with glib2 so you should just try installing that.

jong357 · 08-27-2008, 08:24 AM

Quote:

Originally Posted by Road_map

I think he need gcc-g++-4.2.3-i486-1 package too.

He said he already installed it. config.log also indicates that he did.

Code:

configure:2658: checking for gcc
configure:2674: found /usr/bin/gcc
configure:2685: result: gcc
configure:2923: checking for C compiler version
configure:2930: gcc --version >&5
gcc (GCC) 4.2.3
Copyright (C) 2007 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.

Khue · 08-27-2008, 09:42 AM

I kind of agree with you on the 10.2 thing in retrospect. Once I get this process down, I am going to destroy this box and rebuild it from scratch to make sure everything is clean.

Ok after binutils install, I got further... however still stopping.

Code:

checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... /lib/cpp
configure: error: C preprocessor "/lib/cpp" fails sanity check
See `config.log' for more details.

Here (clicky!) is the config.log file.

Help me with my troubleshooting here, is it failing on trying to include the limits.h header file in the compilation?

gnashley · 08-27-2008, 10:50 AM

Use packages for the version 10.2 if thats what you are running. A minimum of packages which you need for compiling stuff will include: glibc (not the glibc-solibs), kernel-headers, gcc, g++, , cxxlibs, binutils, make, perl, m4, libtool, automake, autoconf and probably bison, flex, gettext, gettext-tools, plus any particular libs needed by the program you are trying to compile.

Khue · 08-27-2008, 11:28 AM

Quote:

Originally Posted by gnashley

...glibc (not the glibc-solibs), kernel-headers...

There we go. After those two were installed we were good to go. I had to use pkg-config from the current slack version b/c 10.2 wasn't new enough. The complete list of things missing or that I needed to make this conference thing work included the following items:

automake-1.9.5 (10.2)
gcc-4.2.3-i486 (10.2)
gcc-g++4.2.3-i486 (not sure)
binutils-2.15.92.0.2-i486 (10.2)
kernel-headers-2.6.13-i386 (10.2)
glibc-2.3.5-i486-6 (10.2)
pkg-config (current)

Holy crap about 50 megs of additionally stuff.

Thanks for the help everyone. I think... (and hope) this gets me to where I need to be.

gnashley · 08-27-2008, 02:50 PM

The pkg-config problem might have been resolved with the nearly 'magic' autoconf command 'autoreconf -if'. Many times when configuration complains because of mis-matched versions of autoconf, automake or libtool, using this command will set things right.
Anyway, glad you got things going. That was a pretty complete list of packages for compiling nearly any sources which use autoconf configuration.