From: Eli Zaretskii <eliz@gnu.org>
To: andrei.elkin@pp.inet.fi
Cc: 28236@debbugs.gnu.org
Subject: bug#28236: 'configure --with-cairo' causes 'emacs -font' to fail
Date: Sat, 26 Aug 2017 10:24:30 +0300 [thread overview]
Message-ID: <838ti67pw1.fsf@gnu.org> (raw)
In-Reply-To: <87a82npghk.fsf@quad> (andrei.elkin@pp.inet.fi)
> From: andrei.elkin@pp.inet.fi
> Date: Fri, 25 Aug 2017 22:57:59 +0300
>
> I've been checking out the master branch periodically for quite a while but never
> configured it with cairo.
> Today I gave it a try, appending the option to my regular option list, as below.
>
> $ git show HEAD
> commit 579890f1c7703cd8ecfe2e56f52cc06fcd1b2442
> Author: Eli Zaretskii <eliz@gnu.org>
> Date: Fri Aug 25 18:01:19 2017 +0300
>
> bash# ./configure --with-xft --with-x-toolkit=lucid --with-dbus \
> --with-cairo && make ...
> => ... [ ok ]
> The resulted executable complains about a font that otherwise
> "orthodoxically" built one never has done (as the font really exists,
> which xlsfonts double-proves:
>
> bash# xlsfonts | grep 7x14
> =>7x14
> ).
>
> bash# src/emacs -Q -font 7x14
> => Font ‘7x14’ is not defined
>
> This effect is observed in earlier commits as well. (I first suspected the
> failure was introduced by a commit in the range started from my last
> pull (about two weeks ago)).
>
> I've not investigated any further, still hope this report is not in
> vain.
Thanks. Unfortunately, we don't have Cairo experts on board, and
we've accumulated several known issues with that configuration. This
is why the configure script says
--with-cairo compile with Cairo drawing (experimental)
^^^^^^^^^^^^
next prev parent reply other threads:[~2017-08-26 7:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-25 19:57 bug#28236: 'configure --with-cairo' causes 'emacs -font' to fail andrei.elkin
2017-08-26 7:24 ` Eli Zaretskii [this message]
2018-12-11 1:50 ` Dmitry Gutov
2018-12-11 6:25 ` Eli Zaretskii
2018-12-12 12:03 ` Ari Roponen
2018-12-12 15:16 ` Eli Zaretskii
2018-12-12 15:41 ` Robert Pluim
2018-12-12 16:37 ` Eli Zaretskii
2018-12-13 11:34 ` Robert Pluim
2018-12-13 13:52 ` Eli Zaretskii
2018-12-13 14:56 ` Robert Pluim
2019-06-04 7:47 ` YAMAMOTO Mitsuharu
2019-06-08 5:13 ` YAMAMOTO Mitsuharu
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=838ti67pw1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28236@debbugs.gnu.org \
--cc=andrei.elkin@pp.inet.fi \
/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).