[ft-devel] Two freetype-2.3.9 problems

[Peter Breitenlohner]

Hi,

I'd like to report the following two freetype-2.3.9 problems (as far as I
can see both already present since quite some time):

(1) You can't invoke freetype's configure script (top-level wrapper) with
an argument '--srcdir=<wherever>', because that isn't properly adjusted when
invoking the real configure script in builds/unix (same for other configure
arguments such as '--cache-file=' and maybe more).

Since such configure arguments are automatically generated (via
AC_CONFIG_SUBDIRS), that makes it very awkward to use freetype as a
subpackage in a larger build system (as we have to do TeX Live).

Do you see any easy solution for that?  I don't think one can directly
invoke the builds/unix/configure script -- or can one?

(2) builds/unix/configure.ac contains this piece of code:

========== cut here == begin piece of code ========
if test ${cross_compiling} = yes; then
  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])

  AC_MSG_CHECKING([for suffix of native executables])
  rm -f a.* b.* a_out.exe conftest.*
  echo > conftest.c "int main() { return 0;}"
  ${CC_BUILD} conftest.c || AC_MSG_ERROR([native C compiler is not working])
  rm -f conftest.c
  if test -x a.out -o -x b.out -o -x conftest; then
    EXEEXT_BUILD=""
  elif test -x a_out.exe -o -x conftest.exe; then
    EXEEXT_BUILD=".exe"
  elif test -x conftest.* ; then
    EXEEXT_BUILD=`echo conftest.* | sed -n '1s/^.*\.//g'`
  fi
  AC_MSG_RESULT($EXEEXT_BUILD)
else
  CC_BUILD=${CC}
  EXEEXT_BUILD=${EXEEXT}
fi


if test ! -z ${EXEEXT_BUILD}; then
  EXEEXT_BUILD=."${EXEEXT_BUILD}"
fi
AC_SUBST(CC_BUILD)
AC_SUBST(EXEEXT_BUILD)
========== cut here == end piece of code ========

With that code you may end up with EXEEXT_BUILD='..exe'!. Cross compiling on
a system with nonempty EXEEXT is certainly quite unlikely, but as far as I
can see EXEEXT_BUILD is also used for build tools in a native build, i.e., a
cygwin build would fail (although I haven't tested this).

That piece of code ought to be

========== cut here == begin piece of code ========
if test ${cross_compiling} = yes; then
  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])

  AC_MSG_CHECKING([for suffix of native executables])
  rm -f a.* b.* a_out.exe conftest.*
  echo > conftest.c "int main() { return 0;}"
  ${CC_BUILD} conftest.c || AC_MSG_ERROR([native C compiler is not working])
  rm -f conftest.c
  if test -x a.out -o -x b.out -o -x conftest; then
    EXEEXT_BUILD=""
  elif test -x a_out.exe -o -x conftest.exe; then
    EXEEXT_BUILD=".exe"
  elif test -x conftest.* ; then
    EXEEXT_BUILD=`echo conftest.* | sed -n '1s/^.*\././'`
  fi
  AC_MSG_RESULT($EXEEXT_BUILD)
else
  CC_BUILD=${CC}
  EXEEXT_BUILD=${EXEEXT}
fi

AC_SUBST(CC_BUILD)
AC_SUBST(EXEEXT_BUILD)
========== cut here == end piece of code ========

Regards
Peter Breitenlohner <address@hidden>