From: Joe Corneli <j.corneli@gold.ac.uk>
To: Glenn Morris <rgm@gnu.org>
Cc: Joe Corneli <j.corneli@gold.ac.uk>, 17043@debbugs.gnu.org
Subject: bug#17043: 24.3.50; xft isn't found on OS X 10.9.2 (Macports)
Date: Thu, 20 Mar 2014 23:37:35 +0000 [thread overview]
Message-ID: <m21txw8mrk.fsf@gold.ac.uk> (raw)
In-Reply-To: <j84n2twoea.fsf@fencepost.gnu.org>
Glenn Morris <rgm@gnu.org> writes:
> Please look in config.log to see what the issue might be.
I found a workaround, but the maintainer of the Xft2 port said that
it isn't correct.
"That sounds like the problem you'd get with software that is not
compatible with freetype 2.5.1 and later. The diff you proposed is not
the correct fix. Consult the freetype documentation for the proper way
to include freetype headers."
- https://trac.macports.org/ticket/42928#comment:5
My workaround patch against /usr/X11/include/ft2build.h was as below:
*** ft2build.h~ Thu Mar 20 22:13:36 2014
--- ft2build.h Thu Mar 20 22:13:46 2014
***************
*** 53,59 ****
#define __FT2_BUILD_UNIX_H__
/* `<prefix>/include/freetype2' must be in your current inclusion path */
! #include <freetype/config/ftheader.h>
#endif /* __FT2_BUILD_UNIX_H__ */
--- 53,59 ----
#define __FT2_BUILD_UNIX_H__
/* `<prefix>/include/freetype2' must be in your current inclusion path */
! #include <freetype2/config/ftheader.h>
#endif /* __FT2_BUILD_UNIX_H__ */
--
Sent with my mu4e
next prev parent reply other threads:[~2014-03-20 23:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 0:12 bug#17043: 24.3.50; xft isn't found on OS X 10.9.2 (Macports) Joe Corneli
2014-03-20 3:16 ` Glenn Morris
2014-03-20 21:58 ` Joe Corneli
2014-03-20 23:37 ` Joe Corneli [this message]
2014-03-23 22:31 ` Joe Corneli
2014-03-23 23:30 ` Glenn Morris
2014-03-25 13:37 ` Joe Corneli
2014-03-25 15:57 ` Glenn Morris
2014-03-26 0:38 ` Stefan Monnier
2014-03-26 0:54 ` Glenn Morris
2014-03-26 16:01 ` Glenn Morris
2014-03-28 2:32 ` Joe Corneli
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=m21txw8mrk.fsf@gold.ac.uk \
--to=j.corneli@gold.ac.uk \
--cc=17043@debbugs.gnu.org \
--cc=rgm@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 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.