all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: esr@thyrsus.com
Cc: jan.h.d@swipnet.se, emacs-devel@gnu.org
Subject: Re: Trunk does not, compile: Missing: ../.bzr/checkout/dirstate
Date: Sun, 12 Jan 2014 20:25:09 +0200	[thread overview]
Message-ID: <8338kt83cq.fsf@gnu.org> (raw)
In-Reply-To: <20140112181549.GB16457@thyrsus.com>

> Date: Sun, 12 Jan 2014 13:15:49 -0500
> From: "Eric S. Raymond" <esr@thyrsus.com>
> Cc: emacs-devel@gnu.org
> 
> Jan Djärv <jan.h.d@swipnet.se>:
> > Hello.
> > 
> > Fresh trunk, run configure, make:
> > 
> > make[1]: *** No rule to make target
> > `../quickfixes/../.bzr/checkout/dirstate', needed by
> > `../../quickfixes/src/../lisp/loaddefs.el'.  Stop.
> > 
> > 	Jan D.
> 
> That's interesting.  Build is not broken for me here

Nor for me.  I test my changes too, you know.

What I broke is the case where the build directory is below the
top-level source directory.  Now fixed.

> but this is clearly Eli's fix going ker-sproing.

Yep, guilty as charged.

> Which I think is rather funny, considering that persions who shall
> remain unnamed are still claiming (incorrectly) that my deletion of
> the broken code made things worse.

I now claim that the original code was not broken at all (and have
restored it completely, erasing my small change that broke Jan's
build).  It "works for me", in the sense that the autoloads target is
invoked when Lisp files change.  Please consider explaining why you
think that code is broken.




  reply	other threads:[~2014-01-12 18:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-12 17:57 Trunk does not, compile: Missing: ../.bzr/checkout/dirstate Jan Djärv
2014-01-12 18:03 ` Eli Zaretskii
2014-01-12 18:04 ` Jan Djärv
2014-01-12 18:15 ` Eric S. Raymond
2014-01-12 18:25   ` Eli Zaretskii [this message]
2014-01-12 18:31   ` Lars Magne Ingebrigtsen

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=8338kt83cq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=esr@thyrsus.com \
    --cc=jan.h.d@swipnet.se \
    /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.