From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: byte-compilation woes (cont'd) Date: Tue, 25 Mar 2014 16:42:39 -0700 Message-ID: <5332146F.4090601@dancol.org> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="WGBNebQQc8sMXfpC7Nm3rnrVL82CsBQp2" X-Trace: ger.gmane.org 1395790961 20400 80.91.229.3 (25 Mar 2014 23:42:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 25 Mar 2014 23:42:41 +0000 (UTC) To: Drew Adams , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 26 00:42:51 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WSazY-0000z2-N6 for ged-emacs-devel@m.gmane.org; Wed, 26 Mar 2014 00:42:48 +0100 Original-Received: from localhost ([::1]:44916 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSazY-0008MS-Bn for ged-emacs-devel@m.gmane.org; Tue, 25 Mar 2014 19:42:48 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58507) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSazU-0008MA-ED for emacs-devel@gnu.org; Tue, 25 Mar 2014 19:42:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WSazT-00027J-2g for emacs-devel@gnu.org; Tue, 25 Mar 2014 19:42:44 -0400 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:60095) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSazS-00025z-M8 for emacs-devel@gnu.org; Tue, 25 Mar 2014 19:42:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=WxWqMOFyhxYmUZ8tIvEvfKLfKGb4p3qsyLYZcHdRZB8=; b=SGaprgbYcJl8ngeLnGHK2s1ysBV28Aok8BmmvmAb4vsq8X3R5FPMH/KyOvZKtTYpnG6T97Ormw/OUIad5JVlz/RG2nLTrQDlSmhgvzX/RNTHx5mq4GRm2xmmpS4mhNb7AaHb6p0tBGmMFY8u1LyvRLzK/ODW3WPlsv0ycQrz1GRt/G1EbEtsvPxJ3gwTzULH3ePwK8gf0QgC4GkC+RKlHvZ8jA/9kcGgOwmvLfmVbvodE+N3kWajb2ER/F6Cx+SB9D3xUwcKSTf3SUQav0mr2ijspj+3zQUHyqpqExGRoE+U0quGaVGU2mJxMhPqoQpEK6c3SrUNXfugrDkIAnXNgQ==; Original-Received: from [2601:8:b200:551::e5a] by dancol.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1WSazR-0007t1-RV; Tue, 25 Mar 2014 16:42:41 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 In-Reply-To: X-Enigmail-Version: 1.6 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:170983 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --WGBNebQQc8sMXfpC7Nm3rnrVL82CsBQp2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 03/25/2014 04:19 PM, Drew Adams wrote: > Just wondering whether there is any way around this... >=20 > With a build from 3/21 I had no problem: >=20 > 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=3D/c/Devel/emacs/snapshot/trunk > --enable-checking=3Dyes,glyphs 'CFLAGS=3D-O0 -g3' 'CPPFLAGS=3D-DGC_MCH= ECK=3D1 > -Ic:/Devel/emacs/include' LDFLAGS=3D-Lc:/Devel/emacs/lib' >=20 > With a build from 3/23 I have a problem: >=20 > 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=3D/c/Devel/emacs/snapshot/trunk > --enable-checking=3Dyes,glyphs 'CFLAGS=3D-O0 -g3' > LDFLAGS=3D-Lc:/Devel/emacs/lib 'CPPFLAGS=3D-DGC_MCHECK=3D1 > -Ic:/Devel/emacs/include'' >=20 > 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. >=20 > (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.) >=20 > 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. >=20 > 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? >=20 > 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 >=20 > 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. --WGBNebQQc8sMXfpC7Nm3rnrVL82CsBQp2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTMhRwAAoJEMAaIROpHW7I9nYP/1/7EMUcZUuxTTgrvvygLdvt pOmssk/u4GfVwh31R94KbyCxSFNKqXNTxRHQwEQ/W4cCPIEtt0D6lkz0DseRseen b7fO7y2TBlSIIZ38l6AJlT4opNFSKNzw2c7T38+FP4EzWrCY/xpVPcPi5luMLzG9 CAfCE0tsUgylmvi1jFTePygnxCnK2M+YZBvHkq8syAaFj5ju20Jlu6qFJn3rWigP N3kJ55r97jWF4rsRO7JgBJNUJjRQOJdyb6IFhIvOAfv9+p/jBWsOiQuuMHybihG4 dIwEUqAflsDBG/v7xWr1uJ+Rn3DWhr9Uzh1jzIs/e1EDlvoj8YqtUe+l8Ir/XKxz vfWbEuCR3HtVUks0CO3L8xy94maeFFFIZR4vFmC8bmbykLIaHTZkTpuPr3b5eTJs ndIHuP77GFDA3qHqMEjjSY3MJzkF8XpG3ytXMZuk/qdaCwlkkyXB7duMY+cAntV4 lBMeSFW+hu+l+2pRl4eaJ/KrZTzn9NF3oljDZmRxQ9Joo2C/63OgW/petlOSfNsM gUtC6GsSmBLM1zmolDCDrZskDDN4Hq3AFRaz2wLqiuLl8zGNOcgHDFDMnxcm5SKG lHmmdQWzNjZQM03QK7EDN4Bzw5az50Xi7RS4OVL59biHZHEFux9txk2cbj174pOi a1cGtdfFWJz3gG4RI4AA =w/qa -----END PGP SIGNATURE----- --WGBNebQQc8sMXfpC7Nm3rnrVL82CsBQp2--