From: Richard Copley <rcopley@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 14503@debbugs.gnu.org
Subject: bug#14503: 24.3.50; MSYS out-of-tree build fails
Date: Sun, 2 Jun 2013 18:58:23 +0100 [thread overview]
Message-ID: <CAPM58oi5Cawi1JBa5WH0JE-9WASkZKubXGepzqZC0tssRdeedQ@mail.gmail.com> (raw)
In-Reply-To: <838v2szass.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 862 bytes --]
[Yet again, sorry for dropping the bug from the CC.]
On 2 June 2013 18:23, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 2 Jun 2013 18:02:07 +0100
> > From: Richard Copley <rcopley@gmail.com>
> > Cc: 14503@debbugs.gnu.org
> >
> > ... but the out-of-tree build is still broken (even with the pre-release
> > make, and without bootstrap).
>
> Not here, sorry.
>
> It sounds like the files it cannot find are all generated by saving
> the autoloads of certain Lisp packages. Did you perhaps inadvertently
> deleted those files?
No. I did this:
bzr clean-tree --unknown --ignored --detritus --verbose --force
bzr revert --no-backup
bzr pull --overwrite
bzr update
before running autogen, configure and make in MSYS.
> If so, does "make autoloads" in the Lisp
> directory solve the problem?
>
Possibly, I will check. But make should still make, right?
[-- Attachment #2: Type: text/html, Size: 1636 bytes --]
next prev parent reply other threads:[~2013-06-02 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 13:49 bug#14503: 24.3.50; MSYS out-of-tree build fails Richard Copley
2013-05-29 17:12 ` Eli Zaretskii
2013-05-29 23:48 ` Richard Copley
2013-06-02 17:02 ` Richard Copley
2013-06-02 17:23 ` Eli Zaretskii
2013-06-02 17:58 ` Richard Copley [this message]
2013-06-02 18:11 ` Richard Copley
2013-06-02 18:16 ` Eli Zaretskii
[not found] ` <CAPM58og7pxE2xW3pc+4WvHoBW_9+GDEbot16pNUPbN949b4_CA@mail.gmail.com>
2013-06-02 19:28 ` Eli Zaretskii
2013-06-02 20:27 ` Richard Copley
2013-06-03 16:59 ` Eli Zaretskii
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=CAPM58oi5Cawi1JBa5WH0JE-9WASkZKubXGepzqZC0tssRdeedQ@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=14503@debbugs.gnu.org \
--cc=eliz@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 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.