Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Hi, I'm trying to build a package, in this case it was a kde theme called 'baghira'. When I tried to run './configure' using the prefix as shown below, the output stated that there is no acceptable C compiler found in the $PATH.
:~/download/baghira-0.8$ ./configure --prefix=`kde-config --prefix` --disable-debug
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/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as requested)
checking for style of include used by make... GNU
checking for gcc... no
checking for cc... no
checking for cc... no
checking for cl... no
configure: error: no acceptable C compiler found in $PATH
See `config.log' for more details.
I checked 'config.log' but it wasn't helpful. To be sure, I tried to build a different package and I got the same error as above.
These looks like the latest version of gcc compilers. Could that have caused the problem? If not, any idea what could be the problem? I'm using debian/etch by the way.
Last edited by garrincha on 2007-01-16 12:00, edited 1 time in total.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
$ dpkg -l|grep gcc
ii gcc 4.1.1-15 The GNU C compiler
ii gcc-3.3-base 3.3.6-15 The GNU Compiler Collection (base package)
ii gcc-3.4-base 3.4.6-5 The GNU Compiler Collection (base package)
ii gcc-4.1 4.1.1-21 The GNU C compiler
ii gcc-4.1-base 4.1.1-21 The GNU Compiler Collection (base package)
ii libgcc1 4.1.1-21 GCC support library
/usr/bin/gcc should be a symlink to your gcc version:
ii gcc-4.1 4.1.1-19 The GNU C compiler
ii gcc-4.1-base 4.1.1-19 The GNU Compiler Collection (base packag$
ii gcj-4.1-base 4.1.1-17 The GNU Compiler Collection (gcj base pa
When I typed 'which gcc', no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.
This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.
Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
mzilikaz, just got around to doing it. I installed gcc as I already have libgcc1. I also made the symlink as well. However, I'm still getting output error, a different one this time:
:~/download/baghira-0.8$ ./configure --prefix=`kde-config --prefix` --disable-debug
checking build system type... i686-pc-linux-gnulibc1
checking host system type... i686-pc-linux-gnulibc1
checking target system type... i686-pc-linux-gnulibc1
checking for a BSD-compatible install... /usr/bin/install -c
checking for -p flag to install... yes
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for kde-config... /usr/bin/kde-config
checking where to install... /usr (as requested)
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.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
Is this not the same thing you are trying to build?
[code]$ aptitude search baghira
p kwin-baghira - KDE theme for Apple junkies :)
[/code]
Yes, this is the same thing. I would have apt-get install it instead however I'm trying to test the compile and build features on my etch installation as I would like to build a kernel later on. Incidentally, I downloaded another tarball kde theme and I tried to run ./configure and I got the same error output as the one for above.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
garrincha wrote:
Yes, this is the same thing. I would have apt-get install it instead however I'm trying to test the compile and build features on my etch installation as I would like to build a kernel later on. Incidentally, I downloaded another tarball kde theme and I tried to run ./configure and I got the same error output as the one for above.
Well I may be the last person you should ask about anything KDE.
You'd have much better luck with a KDE specific forum/mailing list/chat room. Of course, if you find a resolution to your problem it would be great for you to post it so others could read it too.
ii autoconf 2.61-3 automatic configure script builder
ii automake1.9 1.9.6+nogfdl-3 A tool for generating GNU Standards-complian
ii autotools-dev 20060920.1 Update infrastructure for config.{guess,sub}
Keep in mind I'm on a Sid desktop at the moment - package versions are often times different.
ii autoconf 2.61-3 automatic configure script builder
ii automake1.9 1.9.6+nogfdl-3 A tool for generating GNU Standards-complian
ii autotools-dev 20060920.1 Update infrastructure for config.{guess,sub}
Keep in mind I'm on a Sid desktop at the moment - package versions are often times different.
I checked, apparently I did not have these installed, so I installed these packages for the etch version in my installation. Unfortunately, it didn't do the trick.
It is not necessarily a KDE-specific problem. As I mentioned I tried to configure and make a tarball about 2 weeks ago and I got the same error as the one I printed at the top of this trend. I just downloaded the tarball fluxbox-1.0rc2.tar.bz2 and run ./configure and I got the same error.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
ii gcc-4.1 4.1.1-19 The GNU C compiler
ii gcc-4.1-base 4.1.1-19 The GNU Compiler Collection (base packag$
ii gcj-4.1-base 4.1.1-17 The GNU Compiler Collection (gcj base pa
When I typed 'which gcc', no output is returned, so presumedly there is no sym link to the gcc compiler supposedly installed in my system.
This is not the first time that it has happened. I tried to build a package about two weeks ago and I got the same error.
Edit: I checked the /usr/bin/ directory and gcc-4.1 is definitely there.
it looks like you have installed the compiler but not the packages that create the symlinks to the current default compiler.
there should be a package simply named gcc, you need to install it
you might also wan't to install build-essential as there are likely to be other things that are important for building stuff that you don't currently have installed.
I'm still beating around the bush. I am wondering why all of sudden after my debian installaton that was only a couple of weeks old, I could have missed out a lot of stuffs essential in building a package.
I already have gcc and binutils installed. I apt-get 'build-essential' as you suggested plugwash, it dumped
'build-essential g++ g++-4.1 libc6-dev libstdc++6-4.1-dev linux-kernel-headers' into my linux box. It did the trick but up to a point, when trying to './configure' fluxbox, the last line of a very long output:
checking for X... configure: error: Can't find X includes. Please check your installation and add the correct paths
.
What are the required X Window System libraries and header that I needed? Could you please post all the stuffs that I'm supposed to have on my etch installation required to build a package?
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
What exactly is the 'build-dep' package? There doesn't seems to be this package in my etch repo. I'm not trying to install fluxbox from the debian repo, rather I was trying to build a package from the source tarball (i.e., fluxbox-1.0rc2.tar.bz2) that I downloaded from the fluxbox site. If the configure, make and make install doesn't work then it is not likely that I will be able to build my custom kernel.
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
build-dep isn't a package its a command just like update install upgrade dist-upgrade source and so on.
that command will install everything that would be needed to build the debian package of fluxbox which should be pretty much the same as what is needed to build the upstream source.
plugwash wrote:build-dep isn't a package its a command just like update install upgrade dist-upgrade source and so on.
that command will install everything that would be needed to build the debian package of fluxbox which should be pretty much the same as what is needed to build the upstream source.
My bad. I thought that you were talking about a debian package. Anyway, thanks for the tip. I did 'apt-get build-dep fluxbox', and it dumped at least 12M of files in my box specifically:
As you could see, these are devel packages. The ./configure, make and make install did worked when I build fluxbox. But when I tried to test the ./configure for the kde theme (baghira), I got configure error, this time:
checking for Qt... configure: error: Qt (>= Qt 3.0 and < 4.0) (headers and libraries) not found. Please check your installation!
Obviously it looks like that I need to get the Qt headers and libraries. But, shouldn't I have at least all, if not most of the requisted tool for building a package from source?
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."
nearly every library in debian has a corresponding -dev package, installing all of them would be near impossible even if there was a way to find them all.
as i said if there is an older version of the package you are trying to compile in the debian repositries you can use apt-get build-dep to get most of it. Beyond that its a matter of using the package contents search on packages.debian.org and/or some educated guesswork.
dpkg -l|grep qt
ii libqt3-headers 3.3.7-3 Qt3 header files
ii libqt3-mt 3.3.7-3 Qt GUI Library (Threaded runtime version), V
ii libqt3-mt-dev 3.3.7-3 Qt development files (Threaded)
ii libqt3-mt-mysql 3.3.7-3 MySQL database driver for Qt3 (Threaded)
ii python-qt3 3.16-1.2 Qt3 bindings for Python
ii qt3-dev-tools 3.3.7-3 Qt3 development tools
O.k., for future reference when I want to build a custom debian kernel, what is the most important thing that I need to have in order (obviously there are notes/HOW-DOs about it elsewhere that I'm aware of, I'm asking anyway) to have almost trouble free building.
So I would presumed that for a minimal base system install like I did I would be missing out a lot of devel libraries and headers?
Maurice Green on Usain Bolt's 9.58: "The Earth stopped for a second, and he went to Mars."