Fontconfig - Jan 2009 - found reason for `NONE'

[I''ve reported this in the fontconfig bugzilla also.]

This very line in configure.in is the problem:

  fc_cachedir=`eval echo "${localstatedir}/cache/"${PACKAGE}`

In the `configure'' script created with autoconf 2.63 (and probably
other versions too), if the `--prefix'' command line option is not
given, the value of `$localstatedir'' is not correctly expanded yet;
`$prefix'' is still `NONE''.  This leads to compilation commands
like

  ../doltcompile gcc \
    ... \
    -DFC_CACHEDIR=''"NONE/var/cache/fontconfig"'' \
    ...

and to 

  <cachedir>NONE/var/cache/fontconfig</cachedir>

in /usr/local/etc/fonts/fonts.conf.

Until this has been fixed in the sources, a simple workaround is to
always call configure''s `--prefix'' option.


    Werner

On Sat, Jan 17, 2009 at 09:00:07AM +0100, Werner LEMBERG
wrote:
> 
> [I''ve reported this in the fontconfig bugzilla also.]
> 
> This very line in configure.in is the problem:
> 
>   fc_cachedir=`eval echo "${localstatedir}/cache/"${PACKAGE}`
> 
> In the `configure'' script created with autoconf 2.63 (and probably
> other versions too), if the `--prefix'' command line option is not
> given, the value of `$localstatedir'' is not correctly expanded
yet;
> `$prefix'' is still `NONE''.  This leads to compilation
commands like
> 
>   ../doltcompile gcc \
>     ... \
>     -DFC_CACHEDIR=''"NONE/var/cache/fontconfig"''
\
>     ...
> 
> and to 
> 
>   <cachedir>NONE/var/cache/fontconfig</cachedir>
> 
> in /usr/local/etc/fonts/fonts.conf.
> 
> Until this has been fixed in the sources, a simple workaround is to
> always call configure''s `--prefix'' option.
I think the patch below will take care of it. If it was substituted by
configure into, say, fontconfig.pc, it would be more trouble. But we can
just let make DTRT.

--
Dan