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: Tue, 25 Mar 2014 13:37:17 +0000 [thread overview]
Message-ID: <m2siq6762a.fsf@gold.ac.uk> (raw)
In-Reply-To: <jzha6oze5o.fsf@fencepost.gnu.org>
Glenn Morris <rgm@gnu.org> writes:
> So it sounds to me like you need to set CPPFLAGS, LDFLAGS before you run
> configure, so that emacs finds the versions you want it to find. At the
> moment I don't see an Emacs bug here.
Firstly, yes, this does seem to help, but it didn't solve the problem.
$ export CFLAGS='-I/opt/local/include/ -I/opt/X11/include/ -I/opt/local/lib/'
$ export LDFLAGS='-I/opt/local/include/ -I/opt/X11/include/ -I/opt/local/lib/'
$ export CPPFLAGS='-I/opt/local/include/ -I/opt/X11/include/ -I/opt/local/lib/'
For example, Emacs can now find libjpeg and giflib libraries that it
wasn't able to find, before, and it also tries to include the MacPorts
version of Xft. However, here, I still get an error:
In file included from /opt/local/include/X11/Xft/Xft.h:39:
/opt/X11/include/ft2build.h:56:10: fatal error: 'freetype/config/ftheader.h' file not found
Patching this file as I indicated before solves the problem.
I'll try addressing that point to the upstream developer for freetype.
The *possible* Emacs feature request: Shouldn't it be able to detect
that it's being built against MacPorts, and set the relevant flags
automatically?
--
Sent with my mu4e
next prev parent reply other threads:[~2014-03-25 13: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
2014-03-23 22:31 ` Joe Corneli
2014-03-23 23:30 ` Glenn Morris
2014-03-25 13:37 ` Joe Corneli [this message]
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=m2siq6762a.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.