When cross-compiling freetype, when the build compiler executable ends in "-gcc" and CC_BUILD is not set in the environment, configure will fail to find the native compiler and die. The attached patch sets CC_BUILD to ${build}-gcc rather than ${build-gcc}.
I've seen a similar patch in some embedded-centric distros, so this may have been reported before. Is this the correct fix? -- dirtyepic you'd be tossed up or wash up, the narrator relates gentoo org in a spartan antarctican walk for many days 9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8)
diff -Naur freetype-2.3.5-orig/builds/unix/configure.ac freetype-2.3.5/builds/unix/configure.ac --- freetype-2.3.5-orig/builds/unix/configure.ac 2007-07-02 15:41:39.000000000 -0600 +++ freetype-2.3.5/builds/unix/configure.ac 2007-07-17 22:54:26.000000000 -0600 @@ -40,7 +40,7 @@ # checks for native programs to generate building tool if test ${cross_compiling} = yes; then - AC_CHECK_PROG(CC_BUILD, ${build}-gcc, ${build-gcc}) + AC_CHECK_PROG(CC_BUILD, ${build}-gcc, ${build}-gcc) test -z "${CC_BUILD}" && AC_CHECK_PROG(CC_BUILD, gcc, gcc) test -z "${CC_BUILD}" && AC_CHECK_PROG(CC_BUILD, cc, cc, , , /usr/ucb/cc) test -z "${CC_BUILD}" && AC_MSG_ERROR([cannot find native C compiler])
_______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel