From: "Hlöðver Sigurðsson" <hlolli@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 25880@debbugs.gnu.org
Subject: bug#25880: can't build from emacs master branch
Date: Sun, 26 Feb 2017 16:15:10 +0100 [thread overview]
Message-ID: <CAB8vR8KRWBJDpgJn1P1BaQcQoDAULokfORgf6TOsYo6YsxnE=g@mail.gmail.com> (raw)
In-Reply-To: <CAArVCkSqMJj7e9DhuZ3igRUkEjhZCN235zb6yym5Gf6CZ8ukHg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
I did ./config.status && make bootstrap and compilation succeeded without
error.
2017-02-26 15:57 GMT+01:00 Philipp Stephani <p.stephani2@gmail.com>:
>
>
> Hlöðver Sigurðsson <hlolli@gmail.com> schrieb am So., 26. Feb. 2017 um
> 14:29 Uhr:
>
>> I pulled and wanted to build emacs from the master branch, I have a build
>> from january so it's no harm, just thought this information would be useful
>> bug report. Building --with-modules on Fedora25.
>>
>> Loading emacs-lisp/macroexp...
>> Loading cus-face...
>> Loading faces...
>> Loading button...
>> Loading loaddefs.el (source)...
>> Symbol's function definition is void: cl-defgeneric
>> Makefile:546: recipe for target 'emacs' failed
>> make[1]: *** [emacs] Error 255
>> make[1]: Leaving directory '/usr/local/src/emacs/src'
>> Makefile:414: recipe for target 'src' failed
>> make: *** [src] Error 2
>>
>>
> Occasionally source and compiled versions of ELisp libraries get enough
> out of sync that incremental recompilation is no longer possible. Could you
> try:
> ./config.status && make bootstrap
>
[-- Attachment #2: Type: text/html, Size: 2637 bytes --]
prev parent reply other threads:[~2017-02-26 15:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 13:27 bug#25880: can't build from emacs master branch Hlöðver Sigurðsson
2017-02-26 14:57 ` Philipp Stephani
2017-02-26 15:15 ` Hlöðver Sigurðsson [this message]
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='CAB8vR8KRWBJDpgJn1P1BaQcQoDAULokfORgf6TOsYo6YsxnE=g@mail.gmail.com' \
--to=hlolli@gmail.com \
--cc=25880@debbugs.gnu.org \
--cc=p.stephani2@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.
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.