From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: Alan Third <alan@idiocy.org>
Cc: "Charles A. Roelli" <charles@aurox.ch>,
rms@gnu.org, 23753@debbugs.gnu.org, peter_dyballa@freenet.de
Subject: bug#23753: 25.0.95; configuration of X client fails to include graphics libraries on Mac OS X 10.6.8
Date: Tue, 12 Dec 2017 10:31:44 +0900 [thread overview]
Message-ID: <wlindcwx33.wl%mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <20171211210123.GA79080@breton.holly.idiocy.org>
>>>>> On Mon, 11 Dec 2017 21:01:23 +0000, Alan Third <alan@idiocy.org> said:
> Yamamoto san, I hope it’s OK to copy you in on this.
> In order to make the NS port of Emacs compile on GCC on macOS we need
> to remove two instances of Objective‐C blocks in macfont.m. It looks
> to me like we can make it run in‐line, i.e. change
> dispatch_group_async (group, queue, ^{
> glyphs[i] = kCGFontIndexInvalid;
> if (default_uvs_offset)
> {
> struct default_uvs_table *default_uvs =
> (struct default_uvs_table *) ((UInt8 *) uvs
> to just
> {
> glyphs[i] = kCGFontIndexInvalid;
> if (default_uvs_offset)
> {
> struct default_uvs_table *default_uvs =
> (struct default_uvs_table *) ((UInt8 *) uvs
> As far as I can see this will still work, but we’re not sure whether
> it will cause any problems. Since this is, I believe, your code, do
> you have any thoughts on the matter?
Running it in-line wouldn't cause any problems. Actually, the Mac
port based on Emacs 23, which supported older systems that lack
libdispatch and blocks, had conditionals to make it in-line for such
systems:
https://bitbucket.org/mituharu/emacs-mac/src/290e18a99605219116728192433f441db15b97e2/src/macfont.c?at=mac-23&fileviewer=file-view-default#macfont.c-812
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2017-12-12 1:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 12:23 bug#23753: 25.0.95; configuration of X client fails to include graphics libraries on Mac OS X 10.6.8 Peter Dyballa
2016-06-12 12:43 ` Peter Dyballa
2017-12-09 19:16 ` Charles A. Roelli
2017-12-09 20:49 ` Glenn Morris
2017-12-10 10:20 ` Alan Third
2017-12-10 14:58 ` Peter Dyballa
2017-12-10 22:44 ` Alan Third
2017-12-11 0:24 ` Peter Dyballa
2017-12-10 21:44 ` Richard Stallman
2017-12-10 22:42 ` Alan Third
2017-12-11 19:16 ` Charles A. Roelli
2017-12-11 21:01 ` Alan Third
2017-12-12 1:31 ` YAMAMOTO Mitsuharu [this message]
2017-12-12 17:18 ` Alan Third
2017-12-12 17:46 ` Glenn Morris
2017-12-12 19:07 ` Alan Third
2017-12-12 19:17 ` Eli Zaretskii
2017-12-12 20:39 ` Alan Third
2017-12-11 22:35 ` Richard Stallman
2017-12-18 21:16 ` Richard Stallman
2017-12-18 21:21 ` Alan Third
2017-12-19 23:03 ` Richard Stallman
2017-12-10 23:49 ` Glenn Morris
2017-12-10 21:44 ` Richard Stallman
2016-06-13 17:28 ` Glenn Morris
2017-12-08 18:37 ` Glenn Morris
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=wlindcwx33.wl%mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=23753@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=charles@aurox.ch \
--cc=peter_dyballa@freenet.de \
--cc=rms@gnu.org \
/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).