From: Richard Copley <rcopley@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 16099@debbugs.gnu.org
Subject: bug#16099: 24.3.50; Build failure, undefined function `cl-member'
Date: Tue, 10 Dec 2013 18:25:11 +0000 [thread overview]
Message-ID: <CAPM58ohD_joOPHpHR0cJaz+fE6Y4KpnSwDpXY2E7DD3225uAGg@mail.gmail.com> (raw)
In-Reply-To: <1ua9g8o9qu.fsf_-_@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
On 10 Dec 2013 18:12, "Glenn Morris" <rgm@gnu.org> wrote:
>
>
> What's going on here:
>
> Buffer is read-only: #<buffer cus-load.el>
> [...]
> Buffer is read-only: #<buffer finder-inf.el>
> [...]
> Opening output file: no such file or directory,
c:/c/emacs/trunk/lisp/loaddefs.el
> [...]
> loaddefs.el: No such file or directory
>
> ?
That certainly looks suspect, well spotted. I guess
"c:/c/emacs/trunk/lisp/loaddefs.el" is the value of
`generated-autoload-file' which is set a few lines up:
[...] --eval '(setq generated-autoload-file (expand-file-name
"/c/emacs/trunk/lisp/loaddefs.el"))' [...]
I think that's probably a bug (mixing MSYS- and native-style paths), but if
I had used a relative path to invoke the configure script, it would have
been a benign bug. I'll reconfigure using a relative path and try again.
[-- Attachment #2: Type: text/html, Size: 1163 bytes --]
next prev parent reply other threads:[~2013-12-10 18:25 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 12:13 bug#16099: 24.3.50; Build failure, undefined function `cl-member' Richard Copley
2013-12-10 16:46 ` Eli Zaretskii
2013-12-10 16:53 ` Richard Copley
2013-12-10 17:09 ` Glenn Morris
2013-12-10 18:05 ` Eli Zaretskii
2013-12-10 18:13 ` Richard Copley
2013-12-10 18:16 ` Glenn Morris
2013-12-10 18:35 ` Eli Zaretskii
[not found] ` <handler.16099.D16099.138669538824350.notifdone@debbugs.gnu.org>
2013-12-10 17:42 ` bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member') Richard Copley
2013-12-10 17:55 ` Richard Copley
2013-12-10 18:12 ` bug#16099: 24.3.50; Build failure, undefined function `cl-member' Glenn Morris
2013-12-10 18:25 ` Richard Copley [this message]
2013-12-10 18:34 ` Eli Zaretskii
2013-12-10 18:37 ` Richard Copley
2013-12-10 18:59 ` Eli Zaretskii
2013-12-10 20:47 ` Richard Copley
2013-12-10 20:58 ` Eli Zaretskii
2013-12-10 21:08 ` Glenn Morris
2013-12-11 17:07 ` Eli Zaretskii
2013-12-10 18:42 ` Glenn Morris
2013-12-10 18:48 ` Glenn Morris
2013-12-10 18:58 ` Eli Zaretskii
2013-12-10 20:09 ` Dani Moncayo
2013-12-10 20:31 ` Eli Zaretskii
2013-12-10 20:57 ` Dani Moncayo
2013-12-11 17:12 ` Eli Zaretskii
2013-12-12 14:08 ` Dani Moncayo
2013-12-12 16:33 ` Eli Zaretskii
2013-12-12 19:53 ` Dani Moncayo
2013-12-14 9:33 ` Dani Moncayo
2013-12-14 9:56 ` Eli Zaretskii
2013-12-14 20:08 ` Glenn Morris
2013-12-14 21:32 ` Dani Moncayo
2013-12-14 21:43 ` Glenn Morris
2013-12-14 21:56 ` Dani Moncayo
2013-12-10 18:58 ` Eli Zaretskii
2013-12-10 18:13 ` bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member') 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
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=CAPM58ohD_joOPHpHR0cJaz+fE6Y4KpnSwDpXY2E7DD3225uAGg@mail.gmail.com \
--to=rcopley@gmail.com \
--cc=16099@debbugs.gnu.org \
--cc=rgm@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).