From: "Andrei Chițu" <andrei.chitu1@gmail.com>
To: emacs-devel@gnu.org
Subject: Error building Emacs on Linux x64
Date: Thu, 12 Jun 2014 09:41:04 +0300 [thread overview]
Message-ID: <87zjhi3a0v.fsf@aiwass.aiwasshome> (raw)
Hello,
I am trying to compile Emacs from the master branch, on a Debian x64, using
CFLAGS='-O3 -g0 -march=native -pipe' ./configure --enable-link-time-optimization
Using either "make" or "make bootstrap", the build process is terminated with
this error:
In toplevel form:
emacs-lisp/bytecomp.el:2290:1:Warning: `"DEAD"' is a malformed function
emacs-lisp/bytecomp.el:2290:1:Error: Wrong type argument: sequencep, 15505804
Makefile:298: recipe for target 'emacs-lisp/bytecomp.elc' failed
make[3]: *** [emacs-lisp/bytecomp.elc] Error 1
From what I have read in older bug reports, it must be a compiler problem.
This is a recent problem, I have successfully compiled Emacs using the same
configuration on 24 May.
reply other threads:[~2014-06-12 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87zjhi3a0v.fsf@aiwass.aiwasshome \
--to=andrei.chitu1@gmail.com \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).