From: Steve Revilak <steve@srevilak.net>
To: help-gnu-emacs@gnu.org
Subject: Re: compilation errors of trunk version on mac os x expected?
Date: Thu, 20 Jan 2011 22:38:11 -0500 [thread overview]
Message-ID: <20110121033811.GK6009@srevilak.net> (raw)
In-Reply-To: <84893506-22ae-4169-b6df-849d6dc24734@w2g2000yqb.googlegroups.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
>hello, Does anyone know if these compilation error messages are a bug
>or to be expected? I still get occasional crashes and am wondering if
>these are related... cheers, E
>gcc -c -Demacs -DHAVE_CONFIG_H -I. -I/usr/local/emacs/trunk/src -I../
>lib -I/usr/local/emacs/trunk/src/../lib -I/opt/local/include/
>libxml2 -I/opt/local/include/dbus-1.0 -I/opt/local/lib/dbus-1.0/
>include -MMD -MF deps/dbusbind.d -I/opt/local/include -
The compiler command line uses -I/opt/local/include, which I assume is
macports.
Does it make a difference if you take macports out of the picture? I
don't *think* you'd need dbus on OS X, but perhaps I'm wrong.
FWIW, I often use a script like this to create a clean environment for
compilations.
---------------------------------
#!/bin/sh
unset LDFLAGS
unset CFLAGS
unset CXXFLAGS
PATH=`echo $PATH | \
sed 's,:/opt/local/bin,, ; s,:/opt/local/sbin,,'`
export PATH
eval "$@"
---------------------------------
If you called this script "clean-compile", then you'd use it like this
clean-compile ./configure --with-ns
clean-compile make
clean-compile make-install
Hope that helps.
Steve
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-01-21 3:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 7:35 compilation errors of trunk version on mac os x expected? emacs user
2011-01-21 3:38 ` Steve Revilak [this message]
[not found] <mailman.9.1295581100.21031.help-gnu-emacs@gnu.org>
2011-03-05 12:36 ` emacs user
2011-03-05 15:43 ` Matthew L Daniel
[not found] ` <mailman.9.1299339797.13665.help-gnu-emacs@gnu.org>
2011-03-05 18:10 ` emacs user
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=20110121033811.GK6009@srevilak.net \
--to=steve@srevilak.net \
--cc=help-gnu-emacs@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.
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).