From: Glenn Morris <rgm@gnu.org>
To: "Joe Corneli" <holtzermann17@gmail.com>
Cc: 1358@emacsbugs.donarmstrong.com
Subject: bug#1358: error when compiling ftfont.c from CVS
Date: Mon, 17 Nov 2008 20:24:17 -0500 [thread overview]
Message-ID: <ml63ml25dq.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <a9670630811171712u3ed1e876md1e79d8c974d2dd5@mail.gmail.com> (Joe Corneli's message of "Mon, 17 Nov 2008 19:12:33 -0600")
reassign 1358 emacs
stop
"Joe Corneli" wrote:
> 2.1.0
>
> (Which suggests perhaps I should remove the system-pkgconfi package and
> use the fontconfig2-shl?)
Yes, perhaps. fontconfig 2.2.0 or newer should work.
>> What does the configure script output say about fontconfig?
>
> Two lines:
>
> checking GTK_LIBS... -L/sw/lib -L/usr/X11R6/lib -lgtk-x11-2.0
> -lgdk-x11-2.0 -lXrandr -lXinerama -lXext -lXcursor -latk-1.0
> -lgdk_pixbuf-2.0 -lpangoxft-1.0 -lXft -lXrender -lpangox-1.0 -lX11
> -lpangoft2-1.0 -lfontconfig -lfreetype -lpango-1.0 -lm -lgobject-2.0
> -lgmodule-2.0 -lglib-2.0 -lintl -liconv
> checking XFT_LIBS... -L/usr/X11R6/lib -lXft -lfreetype -lXrender -lfontconfig
You don't have a line of the form:
checking for fontconfig >= 2.2.0...
just above the XFT_LIBS part?
It should say "no" if pkg-config reports 2.1.0.
next prev parent reply other threads:[~2008-11-18 1:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <734p22kmt3.fsf@fencepost.gnu.org>
2008-11-16 23:19 ` bug#1358: error when compiling ftfont.c from CVS Joe Corneli
2008-11-17 23:56 ` Glenn Morris
2008-11-18 1:12 ` Joe Corneli
2008-11-18 1:24 ` Glenn Morris [this message]
2008-11-18 1:30 ` Processed: " Emacs bug Tracking System
2008-11-18 2:02 ` Joe Corneli
2008-11-18 2:11 ` Glenn Morris
2008-11-18 2:13 ` Glenn Morris
2008-11-20 3:04 ` Glenn Morris
2008-11-20 23:12 ` Joe Corneli
2008-11-20 23:25 ` bug#1358: marked as done (error when compiling ftfont.c from CVS) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ml63ml25dq.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=1358@emacsbugs.donarmstrong.com \
--cc=holtzermann17@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.