|
From: | GNU bug Tracking System |
Subject: | bug#51104: closed (comp-tests.elc messes up after reconfiguring for different machine) |
Date: | Mon, 12 Sep 2022 20:35:02 +0000 |
Your message dated Mon, 12 Sep 2022 15:34:29 -0500 with message-id <17c80584-7cac-9edf-8c31-632d032f1666@cs.ucla.edu> and subject line Re: bug#51104: comp-tests.elc messes up after reconfiguring for different machine has caused the debbugs.gnu.org bug report #51104, regarding comp-tests.elc messes up after reconfiguring for different machine to be marked as done. (If you believe you have received this mail in error, please contact help-debbugs@gnu.org.) -- 51104: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=51104 GNU Bug Tracking System Contact help-debbugs@gnu.org with problems
--- Begin Message ---Subject: comp-tests.elc messes up after reconfiguring for different machine Date: Fri, 8 Oct 2021 15:59:06 -0700 When trying out the emacs-28 branch on both 32- and 64-bit platforms, I had test failures that I tracked down to this line: User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 test/src/comp-tests.el:933: (integer ,most-negative-fixnum ,most-positive-fixnum))My problem was that I'd built test/src/comp-tests.elc on a 32-bit platform (using "./configure CC='gcc -m32'" on an x86-64 machine) so that .elc file had been built assuming 32-bit values for most-negative-fixnum and most-positive fixnum. When I then re-ran 'configure' for a 64-bit platform the .elc files were not automatically rebuilt for it (they're supposed to be machine-independent, right?) and so the optimizations were incorrect for a 64-bit platform and the tests failed.What's a good way to fix this problem, while still testing everything that comp-tests.el wants to test?
--- End Message ---
--- Begin Message ---Subject: Re: bug#51104: comp-tests.elc messes up after reconfiguring for different machine Date: Mon, 12 Sep 2022 15:34:29 -0500 User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 On 9/12/22 14:34, Andrea Corallo wrote:Probably the quickest and easiest fix is just to add the `no-byte-compile' into comp-tests.el.Thanks for the suggestion. I installed the attached and am closing the bug report.0001-Fix-comp-tests.el-problem-after-reconfiguring.patch
Description: Text Data
--- End Message ---
[Prev in Thread] | Current Thread | [Next in Thread] |