From: Jim Meyering <jim@meyering.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: automake's .el support vs. recent loss of byte-compile-dest-file
Date: Thu, 23 Nov 2017 08:13:58 -0800 [thread overview]
Message-ID: <CA+8g5KH6AkZMZAfSWmtWu=XeG_9FSY0TuAdSt_jgSvXbyRN2Rg@mail.gmail.com> (raw)
In-Reply-To: <8B999815-EA73-4B86-8588-889E1F855A56@gnu.org>
On Wed, Nov 22, 2017 at 10:34 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> On November 23, 2017 7:02:07 AM GMT+02:00, Jim Meyering <jim@meyering.net> wrote:
...
>> However, bear in mind that once that May change makes it into an emacs
>> release, automake-generated Makefile.in files will be broken in that
>> respect.
>
> This incompatible change is not in NEWS. We announced the function
> as obsolete in Emacs 23.2, but evidently Automake didn't take notice.
> So I'd rather we restored that functionality, perhaps with some
> annoying warning to encourage Automake to get their act together
> sooner rather than later. Breaking all the Makefile.in files out there
> doesn't sound TRT to me.
I've just posted an automake fix:
https://lists.gnu.org/archive/html/automake/2017-11/msg00038.html
next prev parent reply other threads:[~2017-11-23 16:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 4:41 automake's .el support vs. recent loss of byte-compile-dest-file Jim Meyering
2017-11-23 4:56 ` Paul Eggert
2017-11-23 5:02 ` Jim Meyering
2017-11-23 6:34 ` Eli Zaretskii
2017-11-23 16:13 ` Jim Meyering [this message]
2017-11-23 16:37 ` Eli Zaretskii
2017-11-27 1:17 ` Jim Meyering
2017-11-27 16:36 ` Eli Zaretskii
2017-11-29 3:35 ` Jim Meyering
2017-11-29 6:44 ` Paul Eggert
2017-11-29 18:23 ` Eli Zaretskii
2017-11-30 2:28 ` Jim Meyering
2017-12-02 11:32 ` Eli Zaretskii
2017-12-02 11:37 ` Eli Zaretskii
2017-12-02 11:57 ` Eli Zaretskii
2017-12-17 0:34 ` Jim Meyering
2017-12-17 15:33 ` Eli Zaretskii
2017-12-04 3:18 ` Glenn Morris
2017-12-04 3:41 ` 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='CA+8g5KH6AkZMZAfSWmtWu=XeG_9FSY0TuAdSt_jgSvXbyRN2Rg@mail.gmail.com' \
--to=jim@meyering.net \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.