all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Copley <rcopley@gmail.com>
To: Glenn Morris <rgm@gnu.org>
Cc: 16099@debbugs.gnu.org
Subject: bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member')
Date: Tue, 10 Dec 2013 17:42:56 +0000	[thread overview]
Message-ID: <CAPM58ohK2z3X42f2vDZ99j1enKpb4L-1oo=p7tmqwHoyxoC4hQ@mail.gmail.com> (raw)
In-Reply-To: <handler.16099.D16099.138669538824350.notifdone@debbugs.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 741 bytes --]

From: Glenn Morris <rgm@gnu.org>

    I'm confident bootstrap will work for you.
    We can reopen this if it does not.

Thanks for your help. So do I now need to be using "make bootstrap" instead
of "make"? Back at bug #14503, Eli told me this:

  Anyway, you don't need "make bootstrap" on the first build with the
  MSYS method.  In fact, you shouldn't need "make bootstrap" at all,
  unless there are deep changes in Lisp that break a normal "make"
  build.  And, contrary to what you say, there's no recommendation to
  bootstrap in INSTALL.MSYS, it says to use just "make".

nt/INSTALL still doesn't say anything about needing to use "make bootstrap".

Like I said, I am using a pristine working tree. You know what that means,
right?

[-- Attachment #2: Type: text/html, Size: 951 bytes --]

  parent reply	other threads:[~2013-12-10 17:42 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   ` Richard Copley [this message]
2013-12-10 17:55     ` bug#16099: closed (Re: bug#16099: 24.3.50; Build failure, undefined function `cl-member') 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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPM58ohK2z3X42f2vDZ99j1enKpb4L-1oo=p7tmqwHoyxoC4hQ@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 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.