all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: yasu@utahime.org, 50285@debbugs.gnu.org
Subject: bug#50285: 28.0.50; Mew dosen't work correctly if .el files of Mew are native compiled
Date: Tue, 31 Aug 2021 15:05:14 +0300	[thread overview]
Message-ID: <83h7f5u8ed.fsf@gnu.org> (raw)
In-Reply-To: <jwvwno2acdw.fsf-monnier+emacs@gnu.org> (bug-gnu-emacs@gnu.org)

> Cc: 50285@debbugs.gnu.org
> Date: Mon, 30 Aug 2021 17:02:08 -0400
> From:  Stefan Monnier via "Bug reports for GNU Emacs,
>  the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> 
> So we really have 3 problems here:
> 
> 1- The code in Mew should not rely on the makefile rule for
>    correct compilation.
>    Fixing this would also make it easier to distribute Mew via ELPA
>    (where a similar problem shows up since package.el will compile the
>    .el files in an unspecified order which could thus result in the
>    same kind of miscompilation).
> 
> 2- The generation of the `.eln` file should start from the `.elc` file
>    rather than from the `.el` file because we sometimes lack the
>    information needed to correctly re-generate the `.elc` file from the
>    `.el` file.

And 3?...





  reply	other threads:[~2021-08-31 12:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 20:38 bug#50285: 28.0.50; Mew dosen't work correctly if .el files of Mew are native compiled Yasuhiro Kimura
2021-08-30 21:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-31 12:05   ` Eli Zaretskii [this message]
2021-08-31 19:01     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-30 17:05 ` Andrea Corallo
2022-08-22 19:01 ` Lars 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=83h7f5u8ed.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50285@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yasu@utahime.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.