From: Eric Brown <brown@fastmail.com>
To: Matthias Pfeifer <mpfeifer77@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Compiling emacs from sources
Date: Wed, 03 May 2017 10:00:49 -0500 [thread overview]
Message-ID: <m2shkmdly6.fsf@fastmail.com> (raw)
In-Reply-To: <CAPzsW6i5nqdA+K=ev+vRAUy4jBuU1FajbWbqi5zS4X2iLNmj2A@mail.gmail.com> (Matthias Pfeifer's message of "Wed, 3 May 2017 16:52:46 +0200")
Matthias Pfeifer <mpfeifer77@gmail.com> writes:
> Im trying to compile emacs from sources. "git status" says there are no
> ...
> remains). If I would be pointed to a solution that would be nice...
>
> Matthias
You may wish to try:
make distclean && ./autogen.sh && ./configure && make bootstrap
where the important differences are claening and adding `bootstrap'.
This has fixed weird build problems for me in the past.
next prev parent reply other threads:[~2017-05-03 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 14:52 Compiling emacs from sources Matthias Pfeifer
2017-05-03 15:00 ` Eric Brown [this message]
2017-05-03 15:03 ` Stephen Berman
[not found] ` <1493824345764.935552.bea03ee40072dc1f15d8e060f1634a68d082d2af@spica.telekom.de>
2017-05-03 16:55 ` Matthias Pfeifer
2017-05-03 20:15 ` tomas
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=m2shkmdly6.fsf@fastmail.com \
--to=brown@fastmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=mpfeifer77@gmail.com \
/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).