Qingy compile missing system headers

pantherlehr · 11-02-2008, 01:11 AM

I'm running Debian etch flavor with a 2.6.18-6-k7 kernel.
I'm trying to compile Qingy v0.9.7 and when I run ./configure I get a list of things that it's checked and at the end it states that "One or more system headers are missing....".

My questions are:
1.) How do I find the name(s)of the system header(s) that it needs to compile?
2.)How do I determine in what package these system headers are contained so that I may install them?

I guess that my problem stems from me not being able to determine the name(s) of this/these file(s). To be honest the answer may be in the config.log file but I have absolutely how to sift that thing.

Any help would be greatly appreciated.

colucix · 11-02-2008, 02:54 AM

Well... the config.log should give you all the answers. Anyway, the first things to check are the requirements. Looking at the FAQ of the Qingy project, you have to previously install DirectFB

Code:

apt-get install libdirectfb-0.9-20 libdirectfb-dev libdirectfb-extra

have you already followed this step?

pantherlehr · 11-02-2008, 04:16 PM

I have attempted to use apt-get to install the following packages:

libdirectfb-0.9-20 libdirectfb-dev libdirectfb-extra.

I seem to have the latest versions of each and every one of them. At least that's what apt-get tells me(libdirectfb-0.9.25 for example).

As for the config.log, it certainly says a lot but just exactly what it says I really can't say.

I suspect that the answer just might be in config.log but I have absolutely no idea how to read it.

Any idea as to what to do next?

colucix · 11-03-2008, 02:29 AM

Well, maybe your system misses some C headers provided from the -dev packages. I'm afraid you have to find out looking at config.log. Open it with a text editor and look for a line like "checking for ANSI C header files" or something similar. Then you will see a list of checks and maybe you will see an error at some point.

Apart the section above, look for other lines like "checking for something.h" and see if there is an error immediately after them. If you want, I can give it a glance if you post the entire config.log here. But please: use CODE TAGS!

pantherlehr · 11-05-2008, 12:44 AM

If you could take a look at it I'd be most appreciative.

Although it does look like there are several errors in this log, I don't know what they mean or to what they refer.

Here's the log in it's entirety (I believe):

Code:

checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/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 recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
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 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 how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... no
checking for g95... no
checking for xlf95... no
checking for f95... no
checking for fort... no
checking for ifort... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for ftn... 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... 98304
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 for correct ltmain.sh version... 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 static flag -static 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 if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
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++ static flag -static 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
(cached) (cached) checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking for a BSD-compatible install... /usr/bin/install -c
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for flex... no
checking for lex... no
checking for bison... no
checking for byacc... no
checking for emacs... no
checking for xemacs... no
checking where .elc files should go... ${datadir}/emacs/site-lisp
checking Checking for gcc version... 4.1.2
Applying architecture optimizations: -march=athlon
checking ctype.h usability... yes
checking ctype.h presence... yes
checking for ctype.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking grp.h usability... yes
checking grp.h presence... yes
checking for grp.h... yes
checking lastlog.h usability... yes
checking lastlog.h presence... yes
checking for lastlog.h... yes
checking paths.h usability... yes
checking paths.h presence... yes
checking for paths.h... yes
checking pthread.h usability... yes
checking pthread.h presence... yes
checking for pthread.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking stdio.h usability... yes
checking stdio.h presence... yes
checking for stdio.h... yes
checking for stdlib.h... (cached) yes
checking signal.h usability... yes
checking signal.h presence... yes
checking for signal.h... yes
checking for string.h... (cached) yes
checking syslog.h usability... yes
checking syslog.h presence... yes
checking for syslog.h... yes
checking termios.h usability... yes
checking termios.h presence... yes
checking for termios.h... yes
checking time.h usability... yes
checking time.h presence... yes
checking for time.h... yes
checking for unistd.h... (cached) yes
checking linux/kd.h usability... yes
checking linux/kd.h presence... yes
checking for linux/kd.h... yes
checking linux/vt.h usability... yes
checking linux/vt.h presence... yes
checking for linux/vt.h... yes
checking sys/ioctl.h usability... yes
checking sys/ioctl.h presence... yes
checking for sys/ioctl.h... yes
checking for sys/types.h... (cached) yes
checking for sys/stat.h... (cached) yes
checking sys/utsname.h usability... yes
checking sys/utsname.h presence... yes
checking for sys/utsname.h... yes
checking sys/wait.h usability... yes
checking sys/wait.h presence... yes
checking for sys/wait.h... yes
checking for dirent.h that defines DIR... yes
checking for library containing opendir... none required
checking for sys/wait.h that is POSIX.1 compatible... (cached) yes
checking for crypt in -lcrypt... yes
checking for dlopen in -ldl... yes
checking for pthread_create in -lpthread... yes
checking for getdomainname... yes
checking curses.h usability... yes
checking curses.h presence... yes
checking for curses.h... yes
checking term.h usability... yes
checking term.h presence... yes
checking for term.h... yes
checking for setupterm in -lncurses... yes
checking for tputs in -lncurses... yes
checking for main in -lpam... no
checking for main in -lshadow... no
checking shadow.h usability... yes
checking shadow.h presence... yes
checking for shadow.h... yes
checking openssl/rsa.h usability... no
checking openssl/rsa.h presence... no
checking for openssl/rsa.h... no
configure: error: One or more system headers that are necessary to compile this program are missing on this system. Cannot continue.

I sincerely hope that this helps some.

Thank-you for any assistance with this issue!!

i92guboj · 11-05-2008, 12:57 AM

You probably need the devel package for openssl, whatever it's called.

colucix · 11-08-2008, 05:56 AM

Sorry for the late reply. I don't see so much errors in the output from configure. Most of the items are found, except for a Fortran compiler (is it really needed?) and the openssl development libraries and headers (as i92guboj pointed out). For these you have to install the libssl-dev package, which contains the rsa.h header file.

Also check the documentation about the fortran compiler requirements. If qingy needs it you can always install one of g77, gfortran or g95.

i92guboj · 11-08-2008, 11:19 PM

Fortran is not required.

pantherlehr · 11-20-2008, 01:37 AM

Well thankx for all of the responses and all of the assistance.

I was finally able to get Qingy to install.

Since I was unable to ascertain the name of the files that ./configure was not finding, I decided to do a little reading. And since the installation of packages/system header files or lack thereof seemed to be a problem I decided to read up on Apt.
In the apt HOWTO I came across a little utility called 'auto-apt' which in my case I could invoke by using the following command:

Code:

auto-apt run ./configure

.

Apparently what this does is call the utility 'auto-apt' which seems to look over the shoulder of whatever command that follows it's invocation. Now as long as the 'auto-apt' database has been updated, this little gem will stop the, in my case, ./configure process whenever ./configure says that it needs something to be installed (or can't find it). Auto-apt will then go find the package that houses said needed file and install it and then let whatever process was stopped continue on its merry way.

There was absolutely no hitch in the ./configure process.
I had no problem with the make process and none with the make install process either.

After I found and used 'auto-apt', the biggest problem that I had was in configuring my inittab file. That took me awhile but I finally got it to work and was greeted with a really nice login screen.

The only problem that I have now is that it (Qingy)....really doesn't work at starting up a session other than a console session. I have several virtual terminals so I'm not hurting but I still have some work to do.

Again, thankx for all of the responses and I hope that this may help some others with similar problems!!

pantherlehr