unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 17300@debbugs.gnu.org
Subject: bug#17300: fails to build due to defsetf, cl-define-compiler-macro in cl-macs.el (structures)
Date: Sun, 20 Apr 2014 17:32:40 +0000	[thread overview]
Message-ID: <871twrhpon.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <83sip8dk3v.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 20 Apr 2014 19:46:44 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> From: Ivan Shmakov  Date: Sun, 20 Apr 2014 16:37:26 +0000

 >> As an aside, I’d gladly be performing all my builds in a clean build
 >> directory, provided that the build system employed by Emacs would
 >> /not/ insist on cluttering $(srcdir).  (As in: with .elc.)

 > I, on the contrary, find a clean build to be a waste of time, and try
 > to avoid it as much as possible.

	That’s why it’s generally possible to reuse build directories
	whether building in or out of $(srcdir).

	Unfortunately, and unlike the majority of the GNU software I’ve
	dealt with, Emacs does not currently allow the user to choose:
	$(srcdir) gets changed irrespective of the use of a separate
	build directory.

	Which makes me wonder if there’s a respective bug somewhere on
	the BTS, or if I should file one myself?

 > There's nothing "unclean" about compiling just the files that were
 > changed since the last update.

	Except that it’s known to break builds if the dependencies are
	incomplete or became broken themselves.

-- 
FSF associate member #7257





  reply	other threads:[~2014-04-20 17:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-20 11:26 bug#17300: fails to build due to defsetf, cl-define-compiler-macro in cl-macs.el (structures) Ivan Shmakov
2014-04-20 11:36 ` Eli Zaretskii
2014-04-20 12:28   ` Daimrod
2014-04-20 13:35   ` Ivan Shmakov
2014-04-20 13:52     ` Eli Zaretskii
2014-04-20 16:37       ` Ivan Shmakov
2014-04-20 16:46         ` Eli Zaretskii
2014-04-20 17:32           ` Ivan Shmakov [this message]
2014-04-20 18:53             ` Eli Zaretskii
2014-04-20 21:58               ` Stefan Monnier
2014-04-20 14:46 ` Daniel Colascione

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=871twrhpon.fsf_-_@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=17300@debbugs.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).