From: Ulrich Mueller <ulm@gentoo.org>
To: 21133@debbugs.gnu.org
Cc: "Toralf Förster" <toralf.foerster@gmx.de>
Subject: bug#21133: Fwd: [Bug 555622] app-editors/emacs-vcs-25.0.50_pre20150630 : ftcrfont.c:109:5: error: ‘ftfont_driver’ undeclared (first use in this function)
Date: Sun, 26 Jul 2015 14:14:06 +0200 [thread overview]
Message-ID: <21940.53006.235403.525884@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <55B3B67F.8090909@gmx.de>
> If I may summarise:
> ./configure --with-cairo --without-xft
> fails with undefined reference to ftfont_driver in ftcrfont.c.
> Perhaps this is simply not a sensible set of configure options to
> use.
Maybe configure should take care of this, and enable cairo only under
the condition that xft is enabled too?
There is a similar problem with --with-cairo --without-png, by the
way. When linking temacs:
image.o:(.data+0x90): undefined reference to `png_load'
> I would also suggest that Gentoo stop enabling --with-cairo,
> and that the --with-cairo option perhaps be labelled experimental.
In fact, our whole app-editors/emacs-vcs package is experimental.
We usually reveal any upstream configure options as USE flags.
(After all, this is not an experimental branch, but git master.)
Of course, I can mask the cairo flag in addition, if you think that's
appropriate.
next prev parent reply other threads:[~2015-07-26 12:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-555622-8324-dDeKezR0sJ@http.bugs.gentoo.org/>
2015-07-25 16:17 ` bug#21133: Fwd: [Bug 555622] app-editors/emacs-vcs-25.0.50_pre20150630 : ftcrfont.c:109:5: error: ‘ftfont_driver’ undeclared (first use in this function) Toralf Förster
2015-07-25 18:35 ` Glenn Morris
2019-06-15 3:57 ` YAMAMOTO Mitsuharu
2015-07-26 12:14 ` Ulrich Mueller [this message]
2015-07-26 15:01 ` Eli Zaretskii
2015-07-27 5:35 ` Ulrich Mueller
2015-07-27 12:33 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21940.53006.235403.525884@a1i15.kph.uni-mainz.de \
--to=ulm@gentoo.org \
--cc=21133@debbugs.gnu.org \
--cc=toralf.foerster@gmx.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).