Your message dated Mon, 12 Aug 2019 22:23:59 +1000
with message-id
<can9bcdtmkdgaucru+rbqu23+owxamx-1kupk-7ddysogcxg...@mail.gmail.com>
and subject line Re: Autoconf freetype2.m4 version checking
has caused the Debian Bug report #183687,
regarding Autoconf freetype2.m4 version checking
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
183687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=183687
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libfreetype6-dev
Version: 2.1.3-10
The AC_CHECK_FT2 macro defined in freetype2.m4 checks for a minimal
version using the output of 'freetype-config --version'. freetype-config
curiously outputs the libtool version instead of the release version,
and there is no trivial relation between these two version, as can be
seen here :
http://cvs.freetype.org/cgi-bin/viewcvs.cgi/freetype2/docs/VERSION.DLL?rev=1.5&content-type=text/vnd.viewcvs-markup
Most importantly, libtool versions do not sort the same wrt. to
lexicographic and chronological orders. Attached is a patch that does
what is suggested by the Freetype doc, ie. parse freetype/freetype.h for
the version macros. It has AC_PROG_CPP as prerequisite since it invokes
$CPP, it's said to be more portable than '$CC -E'.
I am using sid, autoconf 2.57-2, m4 1.4-15 and freetype 2.1.3-10 and CVS
versions.
2a3
> # Vincent Caron 2003-03-06, fixed version checking
46,57c47,53
< ft_config_major_version=`$FT2_CONFIG $ft_config_args --version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'`
< ft_config_minor_version=`$FT2_CONFIG $ft_config_args --version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'`
< ft_config_micro_version=`$FT2_CONFIG $ft_config_args --version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'`
< ft_min_major_version=`echo $min_ft_version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\1/'`
< ft_min_minor_version=`echo $min_ft_version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\2/'`
< ft_min_micro_version=`echo $min_ft_version | \
< sed 's/\([[0-9]]*\).\([[0-9]]*\).\([[0-9]]*\)/\3/'`
---
> ft_version=`echo "FREETYPE_MAJOR.FREETYPE_MINOR.FREETYPE_PATCH" | $CPP
> $FT2_CFLAGS -include freetype/freetype.h - | tail -n1`
> ft_config_major_version=`echo $ft_version | cut -d. -f1`
> ft_config_minor_version=`echo $ft_version | cut -d. -f2`
> ft_config_micro_version=`echo $ft_version | cut -d. -f3`
> ft_min_major_version=`echo $min_ft_version | cut -d. -f1`
> ft_min_minor_version=`echo $min_ft_version | cut -d. -f2`
> ft_min_micro_version=`echo $min_ft_version | cut -d. -f3`
--- End Message ---
--- Begin Message ---
Thank you for your bug report.
freetype2.m4 was removed from Debian's FreeType 2 package last year. I
am therefore closing this bug.
Kind regards,
Hugh
--- End Message ---
