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 21:11:38 -0500 [thread overview]
Message-ID: <mzfxlp3hr9.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <a9670630811171802u2b16d6b8q7d0ccff079d957da@mail.gmail.com> (Joe Corneli's message of "Mon, 17 Nov 2008 20:02:17 -0600")
"Joe Corneli" wrote:
> No, there's no such line -- here's some context:
>
> checking for xft >= 0.13.0... yes
> checking XFT_CFLAGS... -I/usr/X11R6/include -I/usr/X11R6/include/freetype2
> checking XFT_LIBS... -L/usr/X11R6/lib -lXft -lfreetype -lXrender -lfontconfig
> checking X11/Xft/Xft.h usability... yes
I think I see the problem. The configure script has not been
regenerated with some recent changes to the source configure.in.
If you have autoconf >= 2.6.1 installed, running `autoconf' in the
top-level Emacs directory ought to fix it (in the sense that you
should get a successful build without fontconfig). Or you can update
from the repository in a bit.
You still probably want to sort out your fontconfig installation to
get nicer looking fonts in your build.
next prev parent reply other threads:[~2008-11-18 2:11 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
2008-11-18 1:30 ` Processed: " Emacs bug Tracking System
2008-11-18 2:02 ` Joe Corneli
2008-11-18 2:11 ` Glenn Morris [this message]
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=mzfxlp3hr9.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.