Hello there again,

This is a second thread for my installation problem, this time focusing on how to install a package manually.

I try to install Kopete-0.8.4, I found Kopete-0.8.4.tar.gz from the Kopete web site, saved it under Documents/.
I read, read, read and finally learned several command lines.

Thanks to a previous thread I tried to apply the following (blindly I must admit, thanks for adding explaination):

tar xzf kopete-0.8.4.tar.gz
cd kopete-0.8.4
./configure
make
make install

My problem is coming up at the ./configure stage, the answer I get (out of my head sorry for lack of accuracy) is:

no acceptable C compiler on $PATH

Ahem... My questions are:

What is a C compiler?
What went wrong really?
What am I doing actually, here? (as in what is to ./configure, to make or to make install ??)



Please rescue me, if I could install programmes on my machine I would be really happy

Thanks
Kobayashy

What is a C compiler?

A C compiler is a program that turns human readable code into machine lanquage. When you buy a program such as MS Office they dont give you the source code because they do not want you to see how it was made. They have already compiled the program for you, the problem being that if you wanted to change something you would be unable to because you do not have the source code. RPM packages are also precompiled for you so you don't have to compile yourself.

What went wrong really?

The answer is simple that you don't have a C compiler installed on your system. There will be one on the Mandrake CD somewhere. Insert the first CD and see if an option comes up to let you add and remove programs. Then find the C compiler and check it for installation. If you cant find it there you will have to download a C copiler RPM from the internet and install manually.

What am I doing actually, here?

When you run ./configure you are telling the system to check how your computer is set up and what programs are installed that is needed by the one you want to install.

make is a special program that basically compiles the program for you. This is where the C compiler is needed. It will optimize the system depending on what ./configure discovered.

make install

This will install all the currently comiled files all over your system. ie all the library files will be installed in the /lib directories and the execulable (binary) files will be installed in the /bin or /sbin directories.

Thanks, it is all clear now.

I suspect my Mandrake CDs to have a fault, so I wish to download a C compiler from internet and install it.

1- Which C Compiler do you recommend? knowing I have Mandrake 10.0 (if it changes anything)

2- If I need a C Compiler to compile and thus manage to install a programme... How will I be able to install a C Compiler without a C Compiler ? (If you know what I'm trying to say here)

Thanks for the tips.
Kobayashy

If you have urpmi set up, just do (as root) urpmi gcc and it should take care of installing for you.

ok,

I used Mandrake CD to install developement tools and GCC. Now I run again a ./configure on kopete and: i get this...


[kobayashy@localhost kopete-0.8.4]$ ./configure
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... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking whether we are using the GNU C++ compiler... no
checking whether g++ accepts -g... no
checking dependency style of g++... none
checking whether g++ supports -Wmissing-format-attribute... no
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... no
checking whether g++ supports -Wno-long-long... no
checking whether g++ supports -Wnon-virtual-dtor... no
checking how to run the C++ preprocessor... /lib/cpp
configure: error: C++ preprocessor "/lib/cpp" fails sanity check


What do I have to do? cause I don' t know what thhat means....

Cheers

This has been discussed a bit. Try LQ Search for sanity check.

Ok, Sanity Check problem is solved, here is the next error message coming up while trying to configure kopete:

[kobayashy@localhost kopete-0.8.4]$ ./configure
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... gawk
checking whether make sets $(MAKE)... yes
checking for style of include used by make... GNU
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking how to run the C preprocessor... gcc -E
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking whether g++ supports -Wmissing-format-attribute... no
checking whether gcc supports -Wmissing-format-attribute... yes
checking whether g++ supports -Wundef... yes
checking whether g++ supports -Wno-long-long... yes
checking whether g++ supports -Wnon-virtual-dtor... yes
checking whether g++ supports -fno-exceptions... yes
checking whether g++ supports -fno-check-new... yes
checking whether g++ supports -fno-common... yes
checking whether g++ supports -fexceptions... yes
checking how to run the C++ preprocessor... g++ -E
checking whether g++ supports -O0... yes
checking whether g++ supports -Wl,--no-undefined... yes
checking whether g++ supports -Wl,--allow-shlib-undefined... yes
not using lib directory suffix
checking for a sed that does not truncate output... /bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether accepts -g... no
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... no
checking for shl_load in -ldld... no
checking for dlopen... no
checking for dlopen in -ldl... yes
checking whether a program can dlopen itself... yes
checking whether a statically linked program can dlopen itself... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking for shl_load... (cached) no
checking for shl_load in -ldld... (cached) no
checking for dlopen... (cached) no
checking for dlopen in -ldl... (cached) yes
checking whether a program can dlopen itself... (cached) yes
checking whether a statically linked program can dlopen itself... (cached) yes
appending configuration tag "F77" to libtool
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking if C++ programs can be compiled... yes
checking for strlcat... no
checking if strlcat needs custom prototype... yes - in libkdefakes
checking for strlcpy... no
checking if strlcpy needs custom prototype... yes - in libkdefakes
checking for main in -lutil... yes
checking for main in -lcompat... no
checking for crypt in -lcrypt... yes
checking for socklen_t... socklen_t
checking for dnet_ntoa in -ldnet... no
checking for dnet_ntoa in -ldnet_stub... no
checking for inet_ntoa... yes
checking for connect... yes
checking for remove... yes
checking for shmat... yes
checking for sys/types.h... (cached) yes
checking for stdint.h... (cached) yes
checking sys/bitypes.h usability... yes
checking sys/bitypes.h presence... yes
checking for sys/bitypes.h... yes
checking for poll in -lpoll... no
checking CoreAudio/CoreAudio.h usability... no
checking CoreAudio/CoreAudio.h presence... no
checking for CoreAudio/CoreAudio.h... no
checking if res_init needs -lresolv... yes
checking if res_init is available... yes
checking for killpg in -lucb... no
checking for int... yes
checking size of int... 4
checking for short... yes
checking size of short... 2
checking for long... yes
checking size of long... 4
checking for char *... yes
checking size of char *... 4
checking for dlopen in -ldl... (cached) yes
checking for shl_unload in -ldld... no
checking for size_t... yes
checking size of size_t... 4
checking for unsigned long... yes
checking size of unsigned long... 4
checking sizeof size_t == sizeof unsigned long... yes
checking crt_externs.h usability... no
checking crt_externs.h presence... no
checking for crt_externs.h... no
checking for _NSGetEnviron... no
checking for vsnprintf... yes
checking for snprintf... yes
checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include
checking for IceConnectionNumber in -lICE... yes
checking for libXext... yes
checking for pthread_create in -lpthread... yes
checking for extra includes... no
checking for extra libs... no
checking for libz... -lz
checking for libpng... -lpng -lz -lm
checking for libjpeg6b... no
checking for libjpeg... -ljpeg
checking for perl... /usr/bin/perl
checking for Qt... configure: error: Qt (>= Qt 3.2) (library qt-mt) not found. P lease check your installation!
For more details about this problem, look at the end of config.log.
Make sure that you have compiled Qt with thread support!

Wassup now with my Qt, and what is a Qt actually??

Thanks for your help.
K.

Try doing a google search for qt. You'll get to their website, where you can download the source as a tarball. Follow the instructions in the readme file to install it (I'm currently in this process now) .

That's one week I have Mandrake installed I still didn't install any programme...

I found Qt. 3.3, I downloaded it and untared, configured, gmake, make install...and then when I configure kopete it keeps saying I haven't any Qt Lib....
How come?
Did I install my lib in the wrong directory?

K.

To avoid this kind of problems you could install a package using the tool "urpmi", take a look in this post:
http://www.linuxquestions.org/questi...hreadid=203939
moutb did an excellent how-to related with this issue.

Related with manual install of packages (mainly when you didn't find a rpm package for Mandrake), I'm having the same problem when trying to install a package, despite I have QT installed the ./configure says there Qt not found, I'm looking for a way to get round this.

try this: sh ./

I cannot get my Mandrake cd 1,2,or 3 to bring up anything. My bios is in the right order. I tried getting into the iso from a command prompt unsuccessfully. I tried another computer and they all act as if they just ignore the disk.