From: Daniel Colascione <dancol@dancol.org>
To: Drew Adams <drew.adams@oracle.com>, emacs-devel@gnu.org
Subject: Re: byte-compilation woes (cont'd)
Date: Tue, 25 Mar 2014 16:42:39 -0700 [thread overview]
Message-ID: <5332146F.4090601@dancol.org> (raw)
In-Reply-To: <a96ae229-d9a5-43bb-af18-ceb0225fcc94@default>
[-- Attachment #1: Type: text/plain, Size: 2969 bytes --]
On 03/25/2014 04:19 PM, Drew Adams wrote:
> Just wondering whether there is any way around this...
>
> With a build from 3/21 I had no problem:
>
> In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
> of 2014-03-21 on ODIEONE
> Bzr revision: 116829 dancol@dancol.org-20140321121023-5tjxtiws6qa4qyod
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
> `configure --prefix=/c/Devel/emacs/snapshot/trunk
> --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3' 'CPPFLAGS=-DGC_MCHECK=1
> -Ic:/Devel/emacs/include' LDFLAGS=-Lc:/Devel/emacs/lib'
>
> With a build from 3/23 I have a problem:
>
> In GNU Emacs 24.4.50.1 (i686-pc-mingw32)
> of 2014-03-23 on ODIEONE
> Bzr revision: 116869 yamaoka@jpl.org-20140324004210-m3ek4k40qwamyabx
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
> `configure --prefix=/c/Devel/emacs/snapshot/trunk
> --enable-checking=yes,glyphs 'CFLAGS=-O0 -g3'
> LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
> -Ic:/Devel/emacs/include''
>
> Here's the problem. My library help-fns+.el extends help-fns.el
> in various ways. It is compatible with Emacs 22 through 24. Until
> now, you could byte-compile it using Emacs 23 and use the compiled
> file with Emacs 22, 23, or 24 - no problem. Handy for someone (like
> me) who has multiple Emacs versions.
>
> (You could not byte-compile it using 22 or 24 and be able to use
> the result with other versions, however. Emacs 23 was Goldilocks
> for this.)
>
> With the latest Emacs 24 build (from 3/23), I now must byte-compile
> help-fns+.el using that build, to be able to use it with that build.
> And doing that prevents using the compiled file with Emacs 22 or 23.
>
> Worse still. If byte-compiled with the latest build it is not even
> usable with Emacs 24.3 (wrong number of args for `help-window-setup').
I think breaking this way is perfectly reasonable. I don't think we
should invest in downward compatibility of byte-compiled files.
> What is the symptom if you use the library compiled with Emacs 23
> in the latest Emacs 24 build? Buffer *Help* is in Fundamental mode.
> I have no idea why, and I don't really feel like digging into
> finding out why, in hopes that some minor tweak might fix things.
Can you please share the Emacs 23 elc file?
>
> Anyone have an idea what recent change causes this difference
> between a build from 3/21 and a build from 3/23? Anyone see a
> simple fix/workaround to the problem? Thx.
package.el :-D
>
> As Emacs 24.4 is not yet released, I'm hoping this might represent
> just another temporary hiccup from "using a revision from that
> unfortunate period" where an inadvertent mistake crept in
> temporarily. (There's always room for hope, no?) If not, and if
> there is no simple workaround, so be it.
I took a look at the changelog, but no breaking changes are immediately
apparent.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2014-03-25 23:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 23:19 byte-compilation woes (cont'd) Drew Adams
2014-03-25 23:41 ` Juanma Barranquero
2014-03-25 23:45 ` Daniel Colascione
2014-03-26 13:56 ` Drew Adams
2014-03-25 23:42 ` Daniel Colascione [this message]
2014-03-25 23:51 ` Daniel Colascione
2014-03-26 13:57 ` Drew Adams
2014-03-26 13:56 ` Drew Adams
2014-03-26 20:17 ` Drew Adams
2014-03-26 20:18 ` Daniel Colascione
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=5332146F.4090601@dancol.org \
--to=dancol@dancol.org \
--cc=drew.adams@oracle.com \
--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.