NOOB stuck with compiling a program (Kipina) need help


As have fun suggested I am posting my problem in a more appropriate forum.

I am completely new to opensuse (and Linux in general), but I optimistically tried to compile an program and (not suprisinglly)
ran into troubles.

After downloading the program’s tar.gz file and un-taring it I followed the instructions in INSTALL file but got stuck right at the fist step.

After running ./configure this is what I get:

peter@linux-bkzs:~/kipina-0.2.2> ./configure
checking for a BSD-compatible install… /usr/bin/install -c
checking whether build environment is sane… yes
checking for gawk… gawk
checking whether make sets $(MAKE)… yes
checking whether to enable maintainer-specific portions of Makefiles… no
checking for intltool >= 0.21… 0.35.0 found
checking for perl… /usr/bin/perl
checking for XML::Parser… ok
checking for iconv… /usr/bin/iconv
checking for msgfmt… /usr/bin/msgfmt
checking for msgmerge… msgmerge
checking for xgettext… xgettext
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 for style of include used by make… GNU
checking dependency style of gcc… gcc3
checking for a BSD-compatible install… /usr/bin/install -c
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.exe… 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 build system type… i686-pc-linux-gnu
checking host system type… i686-pc-linux-gnu
checking for a sed that does not truncate output… /usr/bin/sed
checking for grep that handles long lines and -e… /usr/bin/grep
checking for egrep… /usr/bin/grep -E
checking for ld used by gcc… /usr/i586-suse-linux/bin/ld
checking if the linker (/usr/i586-suse-linux/bin/ld) is GNU ld… yes
checking for /usr/i586-suse-linux/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 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 g77… no
checking for f77… no
checking for xlf… 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 f90… no
checking for xlf90… no
checking for pgf90… no
checking for pghpf… no
checking for epcf90… no
checking for gfortran… no
checking for g95… no
checking for f95… no
checking for fort… no
checking for xlf95… 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… 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 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/i586-suse-linux/bin/ld) supports shared libraries… yes
checking whether -lc should be explicitly linked in… no
checking dynamic linker characteristics… GNU/Linux
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… no
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
appending configuration tag “F77” to libtool
checking for pkg-config… /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0… yes
checking for GTK… configure: error: Package requirements (gtk±2.0 >= 2.4.0) were not met:

No package ‘gtk±2.0’ found

Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.

Alternatively, you may set the environment variables GTK_CFLAGS
and GTK_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.

What to do to solve this mess and get the program compiled and working (if possible) and more important any good tips on internet web resources, books, turtorials or how to’s on bash command line work and programs compiling for complete beginners.

Thank you!

As a general rule of thumb,when compiling you need to have kernel-sources,make,gcc/gcc++ installed. Sometimes,the readme that comes with the file tells you if you may need anything else. Installing development files also helps


> What to do to solve this mess and get the program compiled and working

open YaST > give root pass when asked > click on Software Management
> take a snooze (it is slow…so wait) > when the new window come up
steady, on the left top side there is a line “Filter:” it is probably
set to “Search” > spin it to “Patterns” and the pane below will
update, scroll down to the “Development” area and > click to place a
check mark in these sections:

  • Base Development
  • KDE Development (if you use KDE)
  • GNOME Development (if you use GNOME)
  • C/C++ Development
  • QT 4 Development

then, go back to that top block that you set to “Patterns” and spin
it back to “Filter” > type kernel in the search blank and click the
“Search” button, eventually the right pane will update and scroll
down until you find “kernel-source” and click to put a check mark in
the little box…

then click “Accept” at the bottom right

after whiring and thinking it will finish…and, maybe close, or
maybe you have to click to close it…

if all went well you can now go back and try to compile again…maybe
it will work (keep reading)

> (if possible) and more important any good tips on internet web
> resources, books, turtorials or how to’s on bash command line work and
> programs compiling for complete beginners.

compiling is pretty easy really (i KNOW it is not the first time, nor
the second…but it gets easier) just remember to do the config and
make as a normal user and then the install as root…

AND, always READ the bottom of the output: it will TELL you what is
missing…the big thing missing for your first attempt was “No
package ‘gtk±2.0’ found”…if the second time there are now errors
or warnings at the bottom of the ./configure, then you are ready
to take the next step…i suppose ‘make’ or whatever the readme says…

if it runs ok (no warnings or errors) then install or whatever the
readme says [hey, if it is a readme for Windows[tm] you are reading
the WRONG readme]

the mantra:
1 try
2 read the output
3 learn what is missing
4 go back to YaST and find/install it
5 begin again at step 1

as for basic info…the web is FULL of it…try google, or here are
some really good sources (for some things):

there are thousands of others:
google (for example) linux help beginner

you will soon find you are surrounded by friends!
lots of them helpful, some not so much…and, VERY FEW willing to do
YOUR required reading and telling you what to do next.

have fun

Hear this piece of advice, It took me a while to figure this out. The development files usually end in devel or dev. Look for them in Yast, depending on the error the console marks.

Did as you told me and the program is now working.

I was actually searching in the package manager for this gtk lib but it was already installed, didn’t try to install any thing with development ending as I thought I’m not developing, just installing… but until now I newer used the Pattern option (it turns out it is weary useful as it groups the relevant packages together).



I have followed your hints, installed the development files and now the program WORKS :)!!

The thing is, while finding a bunch of development packages in Software Manager I didn’t know I need them.

Thank you everyone for your help!