--- Begin Message ---
Subject: |
26.0.50; ede-proj-elisp-add-path |
Date: |
Fri, 07 Jul 2017 14:30:55 +0200 (CEST) |
Hi,
Produces an error when searching for regexp in
elisp-comp. Searched regexp is not in this file that is
sufficiently small to be manually explored.
Maybe an version incompatiblity but
autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
And :
automake --version
automake (GNU automake) 1.12.4
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Tom Tromey <tromey@redhat.com>
and Alexandre Duret-Lutz <adl@gnu.org>.
I think that elisp-comp that is automatically installed comes
from one of tese two packages.
Regards
Pierre
In GNU Emacs 26.0.50 (build 1,
x86_64-pc-linux-gnu) of 2017-07-07 built on jabberwocky
Repository revision: 579a9ee22e0decf7bed8aff1751c5b3d147b921f
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#27608: 26.0.50; ede-proj-elisp-add-path |
Date: |
Mon, 10 Aug 2020 10:09:42 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) |
Pierre Lorenzon <devel@pollock-nageoire.net> writes:
> I think that the most reasonnable answer is : update automake
> to 1.15. elisp-comp will simply disappear (this was reported in
> a previous emacs bug report). All problems due to elisp-comp
> will disappear as well except a warning signaling that is does
> not exist : but do not care about that ! .el file will compile
If I read this correctly, the issue was resolved by upgrading automake.
I'm therefore closing this bug report now. If this conclusion is
incorrect, please reply to this email (use "Reply to all" in your email
client) and we can reopen the bug report.
Best regards,
Stefan Kangas
--- End Message ---