I'm new to Cairo and I'm attempting to build the latest version (1.6.4) from source on a CentOS 4.4 kernel: [root@corp03 pixman-0.10.0]# uname -r 2.6.9-42.ELsmp When I run a ./configure --prefix=/usr I get ... ... ... ... checking for pkg-config... /usr/local/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for pixman... no configure: error: pixman >= 0.10.0 is required (http://cairographics.org/releases/) From looking at the configure shell script, it appears that the pixman_CFLAGS is not being set. This makes configure fail at or rear line 21388. I've try setting the pixman_CFLAGS environment variable, but configure doesn't seem to recognize it. I'm not sure what to do next and I really need this to work...please help. See additional info below: Pixman is built here: [root@corp03 pixman-0.10.0]# make install Making install in pixman make[1]: Entering directory `/root/pixman-0.10.0/pixman' make[2]: Entering directory `/root/pixman-0.10.0/pixman' test -z "/usr/lib" || /bin/mkdir -p "/usr/lib" /bin/sh ../libtool --mode=install /usr/bin/install -c 'libpixman-1.la' '/usr/lib/libpixman-1.la' /usr/bin/install -c .libs/libpixman-1.so.0.10.0 /usr/lib/libpixman-1.so.0.10.0 (cd /usr/lib && { ln -s -f libpixman-1.so.0.10.0 libpixman-1.so.0 || { rm -f libpixman-1.so.0 && ln -s libpixman-1.so.0.10.0 libpixman-1.so.0; }; }) (cd /usr/lib && { ln -s -f libpixman-1.so.0.10.0 libpixman-1.so || { rm -f libpixman-1.so && ln -s libpixman-1.so.0.10.0 libpixman-1.so; }; }) /usr/bin/install -c .libs/libpixman-1.lai /usr/lib/libpixman-1.la /usr/bin/install -c .libs/libpixman-1.a /usr/lib/libpixman-1.a chmod 644 /usr/lib/libpixman-1.a ranlib /usr/lib/libpixman-1.a PATH="$PATH:/sbin" ldconfig -n /usr/lib ---------------------------------------------------------------------- Libraries have been installed in: /usr/lib If you ever happen to want to link against installed libraries in a given directory, LIBDIR, you must either use libtool, and specify the full pathname of the library, or use the `-LLIBDIR' flag during linking and do at least one of the following: - add LIBDIR to the `LD_LIBRARY_PATH' environment variable during execution - add LIBDIR to the `LD_RUN_PATH' environment variable during linking - use the `-Wl,--rpath -Wl,LIBDIR' linker flag - have your system administrator add LIBDIR to `/etc/ld.so.conf' See any operating system documentation about shared libraries for more information, such as the ld(1) and ld.so(8) manual pages. ---------------------------------------------------------------------- test -z "/usr/include/pixman-1/" || /bin/mkdir -p "/usr/include/pixman-1/" /usr/bin/install -c -m 644 'pixman.h' '/usr/include/pixman-1//pixman.h' /usr/bin/install -c -m 644 'pixman-version.h' '/usr/include/pixman-1//pixman-version.h' make[2]: Leaving directory `/root/pixman-0.10.0/pixman' make[1]: Leaving directory `/root/pixman-0.10.0/pixman' Making install in test make[1]: Entering directory `/root/pixman-0.10.0/test' make[2]: Entering directory `/root/pixman-0.10.0/test' make[2]: Nothing to be done for `install-exec-am'. make[2]: Nothing to be done for `install-data-am'. make[2]: Leaving directory `/root/pixman-0.10.0/test' make[1]: Leaving directory `/root/pixman-0.10.0/test' make[1]: Entering directory `/root/pixman-0.10.0' make[2]: Entering directory `/root/pixman-0.10.0' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/usr/lib/pkgconfig" /usr/bin/install -c -m 644 'pixman-1.pc' '/usr/lib/pkgconfig/pixman-1.pc' make[2]: Leaving directory `/root/pixman-0.10.0' make[1]: Leaving directory `/root/pixman-0.10.0' pkg-config verifies that Pixman is at version 0.10.0 [root@corp03 ~]# /usr/local/bin/pkg-config --modversion /usr/lib/pkgconfig/pixman-1.pc 0.10.0 [root@corp03 ~]#
config.log would have more information, but from reading the process there, the one thing that springs to mind is running ldconfig to set up the links for the new libpixman-1.so.
Old build failure due to system configuration.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.