unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50569@debbugs.gnu.org
Subject: bug#50569: 28.0.50; [native-comp] emacs-lisp-native-compile-and-load does not load require'd files before compiling
Date: Thu, 25 Aug 2022 17:05:52 -0500	[thread overview]
Message-ID: <be589ebf-6847-9f4c-84fd-e7155f8397ad@alphapapa.net> (raw)
In-Reply-To: <87h720gxqg.fsf@gnus.org>

Hi Lars,

Thanks for following up on this.

On 8/25/22 10:16, Lars Ingebrigtsen wrote:
> Adam Porter <adam@alphapapa.net> writes:
> 
>> *Expected results:* + Compilation succeeds without errors or 
>> warnings. + Macro ~bar-define-key~ is defined. + Function 
>> ~bar-key-baz~ is defined.
>> 
>> *Actual results:* Neither the macro nor the function are defined, 
>> and these warnings are displayed in =*Compile-Log*=:
> 
> (I'm going through old bug reports that unfortunately weren't 
> resolved at the time.)
> 
> I'm unable to reproduce this problem in Emacs 29 -- do you still see 
> this problem with the current master?

I'm afraid I don't have time to test that myself right now.  If you were
unable to reproduce it with the recipe I provided, I'd guess that it's
been solved in version 29.

If it's possible to backport a fix to version 28, that would be
good, because if that version ends up being included in various
distributions and used for years, it would mean that Emacs packages
could have to workaround this problem for years as well.  (Or, of
course, they could declare Emacs 29 as the minimum required version,
which will lead users on version 28 to complain...you know the drill.)





  reply	other threads:[~2022-08-25 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 13:41 bug#50569: 28.0.50; [native-comp] emacs-lisp-native-compile-and-load does not load require'd files before compiling Adam Porter
2022-08-25 15:16 ` Lars Ingebrigtsen
2022-08-25 22:05   ` Adam Porter [this message]
2022-08-26 10:59     ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be589ebf-6847-9f4c-84fd-e7155f8397ad@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=50569@debbugs.gnu.org \
    --cc=larsi@gnus.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).