teh_sAbEr Posted July 29, 2004 Report Share Posted July 29, 2004 ive been having some problemss installing (compile from source) Pango 1.4.0. i keep getting an error during ./configure that says GLib isn't version 2.4.0 and above, but i know i installed version 2.4.4. any way to "point" it at where i installed GLib (/usr/local/lib i think..)? thanks! heres the output of ./configure [root@pldt pango-1.4.0]# ./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 for native Win32... no 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 for style of include used by make... GNU checking dependency style of gcc... gcc3 checking for c++... c++ checking whether we are using the GNU C++ compiler... yes checking whether c++ accepts -g... yes checking dependency style of c++... gcc3 checking build system type... i686-redhat-linux-gnu checking host system type... i686-redhat-linux-gnu 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 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 how to run the C++ preprocessor... c++ -E checking for g77... g77 checking whether we are using the GNU Fortran 77 compiler... yes checking whether g77 accepts -g... yes 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 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 c++... /usr/bin/ld checking if the linker (/usr/bin/ld) is GNU ld... yes checking whether the c++ linker (/usr/bin/ld) supports shared libraries... yes checking for c++ option to produce PIC... -fPIC checking if c++ PIC flag -fPIC works... yes checking if c++ supports -c -o file.o... yes checking whether the c++ 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 appending configuration tag "F77" to libtool checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... no checking for g77 option to produce PIC... -fPIC checking if g77 PIC flag -fPIC works... yes checking if g77 supports -c -o file.o... yes checking whether the g77 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 some Win32 platform... no checking for perl5... perl5 checking for X... libraries /usr/X11R6/lib, headers /usr/X11R6/include checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking for pkg-config... /usr/bin/pkg-config checking for fontconfig >= 1.0.1... yes checking FONTCONFIG_CFLAGS... checking FONTCONFIG_LIBS... -lfontconfig checking for freetype-config... /usr/bin/freetype-config checking for FT_Get_Next_Char in -lfreetype... yes checking for xft >= 2.0.0... yes checking XFT_CFLAGS... -I/usr/X11R6/include -I/usr/include/freetype2 checking XFT_LIBS... -L/usr/X11R6/lib -lXft -lX11 -lfreetype -lXrender -lfontconfig checking for pkg-config... (cached) /usr/bin/pkg-config checking for GLIB - version >= 2.4.0... no *** Could not run GLIB test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GLIB is incorrectly installed. configure: error: *** Glib 2.4.0 or better is required. The latest version of *** Glib is always available from ftp://ftp.gtk.org/. Quote Link to comment Share on other sites More sharing options...
tyme Posted July 30, 2004 Report Share Posted July 30, 2004 you should be able to do: ./configure --glib-prefix=/usr/local or something similar. see: ./configure --help to find the correct option. you realise that it's quite possible that upgrading glib, pango, and all of these others via source could cause problems, right? especially if you have 2 concurrent glibs on your system...(one in /usr/local and one in /usr). Quote Link to comment Share on other sites More sharing options...
teh_sAbEr Posted July 30, 2004 Author Report Share Posted July 30, 2004 you should be able to do: ./configure --glib-prefix=/usr/local or something similar. see: ./configure --help to find the correct option. you realise that it's quite possible that upgrading glib, pango, and all of these others via source could cause problems, right? especially if you have 2 concurrent glibs on your system...(one in /usr/local and one in /usr). <{POST_SNAPBACK}> really? didn't realize that, thx for the info. i wuz hoping to upgrade to GIMP 2.0.3, which requires GTK, which requires pango, atk, pkgconfig, etc. Quote Link to comment Share on other sites More sharing options...
tyme Posted July 30, 2004 Report Share Posted July 30, 2004 GTK is on the CD's, you can install it via RPM through Mandrake Control Center -> Install software. If you're trying to install gimp from source and it's not work this is because you need the gtk2-devel package installed to compile it. this can also be found in Install Software as it's included on the CDs. anytime you compile something from source for an RPM based distro (and some others) you need to install the -devel package for anything that piece of software requires. Quote Link to comment Share on other sites More sharing options...
teh_sAbEr Posted July 30, 2004 Author Report Share Posted July 30, 2004 thanx for d help. pango still not working though. how about using URPMI to install this stuff? im not too familiar w/it but i heard it solves dependency problems. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.