Dear All,
I am trying to install Anjuta 1.1.1 on my RedHat 9.0 But I am facing following problem.
root@sachin anjuta-1.1.1]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal-1.4... found
checking for working autoconf... found
checking for working automake-1.4... found
checking for working autoheader... found
checking for working makeinfo... found
checking for perl... /usr/bin/perl
checking for gcc... gcc
checking for C compiler default output... 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 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 for strerror in -lcposix... no
checking for ANSI C header files... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
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 dependant libraries... pass_all
checking command to parse /usr/bin/nm -B output... ok
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 ranlib... ranlib
checking for strip... strip
checking for objdir... .libs
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 if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions... yes
checking whether the linker (/usr/bin/ld) supports shared libraries... yes
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking whether -lc should be explicitly linked in... no
creating libtool
checking return type of signal handlers... void
checking for pkg-config... /usr/bin/pkg-config
checking for glib-2.0 >= 2.0.6 gtk+-2.0 >= 2.0.8 ORBit-2.0 >= 2.4
.0 libglade-2.0 >= 2.0.0 libgnome-2.0 >= 2.0.2 libgnomeui-2.0 >= 2.0.2l
ibgnomeprint-2.2 >= 2.0.1 libgnomeprintui-2.2 >= 2.0.1 gnome-vfs-2.0 >=
2.0.2 gnome-vfs-module-2.0 >= 2.0.2 libbonobo-2.0 >= 2.0.0 libbonoboui-2.0
>= 2.0.1 vte >= 0.7.0 libzvt-2.0 >= 2.0.0 libxml-2.0 >= 2.4.23 p
ango >= 1.1.1... Package glib-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `glib-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'glib-2.0' found
configure: error: Library requirements ( glib-2.0 >= 2.0.6 gtk+-2.0
>= 2.0.8 ORBit-2.0 >= 2.4.0 libglade-2.0 >= 2.0.0 libgnome-2.0 >=
2.0.2 libgnomeui-2.0 >= 2.0.2 libgnomeprint-2.2 >= 2.0.1 libgnome
printui-2.2 >= 2.0.1 gnome-vfs-2.0 >= 2.0.2 gnome-vfs-module-2.0 >= 2.0.2 l
ibbonobo-2.0 >= 2.0.0 libbonoboui-2.0 >= 2.0.1 vte >= 0.7.0 libzvt-2
.0 >= 2.0.0 libxml-2.0 >= 2.4.23 pango >= 1.1.1) not met; consider adjust
ing the PKG_CONFIG_PATH environment variable if your libraries are in a nonstand
ard prefix so pkg-config can find them.
[root@sachin anjuta-1.1.1]#
Kindly give me some suggestions to solve this Problem.
