unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 11649@debbugs.gnu.org
Subject: bug#11649: 24.1.50; Some compilation woes
Date: Wed, 13 Jun 2012 10:12:35 -0400	[thread overview]
Message-ID: <jwv8vfr9u9u.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vcizrw2r.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 10 Jun 2012 19:05:48 +0300")

>> > If so, this scenario cannot explain the problem, because cl-macs.el is
>> > compiled exactly once during bootstrap; before the compilation there's
>> > only cl-macs.el.
>> Then, we need to investigate the real source of the problem.
>> Does someone have a reproducible recipe for it?
> The way I did it was to wait until the bootstrap version of Emacs,
> with all the preloaded Lisp files in .el form, dumps itself during
> bootstrap, then copy the executable aside, and use it for compiling
> whatever Lisp files I wanted.
> Andreas suggested a different recipe, which I think is equivalent.

I could swear I saw Andreas's recipe, but I can't find it again in
my emails.  Could someone resend it, please?


        Stefan





  reply	other threads:[~2012-06-13 14:12 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 13:19 bug#11649: Some compilation woes Juanma Barranquero
2012-06-09  9:29 ` bug#11649: 24.1.50; " Eli Zaretskii
2012-06-09 10:05   ` Juanma Barranquero
2012-06-09 11:41     ` Eli Zaretskii
2012-06-09 19:28       ` Juanma Barranquero
2012-06-10  2:52         ` Eli Zaretskii
2012-06-09 10:14   ` martin rudalics
2012-06-09 11:38     ` Eli Zaretskii
2012-06-09 13:02       ` martin rudalics
2012-06-10  1:08   ` Stefan Monnier
2012-06-10  2:59     ` Eli Zaretskii
2012-06-10 14:40       ` Stefan Monnier
2012-06-10 16:05         ` Eli Zaretskii
2012-06-13 14:12           ` Stefan Monnier [this message]
2012-06-13 15:35             ` Eli Zaretskii
2012-06-13 16:39               ` Stefan Monnier
2012-06-14  3:06                 ` Eli Zaretskii
2012-06-14  3:32                   ` Stefan Monnier
2012-06-14 17:10                     ` Eli Zaretskii
2012-06-14 17:56                       ` Glenn Morris
2012-06-14 18:27                         ` Juanma Barranquero
2012-06-14 19:28                         ` Eli Zaretskii
2012-06-15 17:45                         ` Juanma Barranquero
2012-06-15 18:27                           ` Eli Zaretskii
2012-06-15 19:22                             ` Juanma Barranquero
2012-06-14 17:51                 ` Glenn Morris
2012-06-12 21:35   ` Juanma Barranquero
2012-06-12 22:27     ` Glenn Morris
2012-06-12 22:39       ` Glenn Morris
2012-06-13 11:09         ` Juanma Barranquero
2012-06-13 12:56           ` Stefan Monnier
2012-06-15  3:19           ` Stefan Monnier
2012-06-13 12:48         ` Stefan Monnier

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=jwv8vfr9u9u.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11649@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lekktu@gmail.com \
    /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).