Dan Nicholson wrote:
> On Wed, Jul 23, 2008 at 7:34 AM, Dan McGhee <[EMAIL PROTECTED]> wrote:
>
>> <irrelevant snippe>
>>
>>
>> $PKG_CONFIG_PATH=/usr/bin/pkg-config:/usr/lib/pkgconfig:/usr/share:/usr/include
>>
>
> I'm not sure if this setting is causing the problems, but it's not
> correct. PKG_CONFIG_PATH should only contain paths where there is .pc
> metadata files. So, a valid setting would be
> PKG_CONFIG_PATH=/usr/lib/pkgconfig:/usr/share/pkgconfig. However,
> those two paths are the default search path, so if you're only
> installing in /usr, you can omit PKG_CONFIG_PATH entirely.
>
This is what I thought also, and when $PKG_CONFIG_PATH turned up empty,
I put the other things in to hopefully make sure I was covering all the
bases. No joy.
> You can test this easily enough:
>
> $ pkg-config --modversion fontconfig
> $ pkg-config --cflags fontconfig
> $ pkg-config --libs fontconfig
> $ pkg-config --cflags "fontconfig >= 2.2"
> $ pkg-config --libs "fontconfig >= 2.2"
>
> The last two commands being what configure is doing, but storing the
> results in FONTCONFIG_{CFLAGS,LIBS}. Maybe your fontconfig is too old?
>
I installed fontconfig 2.4.2 for this BLFS build. Interesting results
from all of those commands. They all give
<verbage telling me "couldn't find fontconfig in the search path"> Maybe
you should consider putting the directory containing "fontconfig.pc" in
PKG_CONFIG_PATH.
`find / -xdev -type f -name "fontconfig.pc" -print` gave nothing. I use
the "more control" package management system and the file list did not
indicate installing this file at all. Fontconfig does install it doesn't
it? Checked my logs and I did everything according to the book. Hmmm.
I'll unpack the source again and see if I can find anything.
<snipped more irrelevant>
>> I didn't even get any "me too's" when I googled and found
>> nothing similar in the archives. Therefore, I'm assuming that it was
>> something I did or overlooked.
>>
>
> Yeah, this seems like a configuration error rather than in the source
> of Xft or fontconfig. Try the commands above; if they're failing, then
> there's no reason to continue until they're resolved.
>
Yup!! This could be a show stopper.
Thanks, Dan.
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
