unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Andrea Corallo <akrl@sdf.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Manuel Uberti <manuel.uberti@inventati.org>,
	53596@debbugs.gnu.org
Subject: bug#53596: 29.0.50; comp-trampoline-compile: Cannot find suitable directory for output in `native-comp-eln-load-path'
Date: Sat, 29 Jan 2022 18:36:31 +0100	[thread overview]
Message-ID: <87fsp6zbog.fsf@web.de> (raw)
In-Reply-To: <xjfmtjfvvir.fsf@ma.sdf.org> (Andrea Corallo's message of "Sat, 29 Jan 2022 07:41:32 +0000")

Andrea Corallo <akrl@sdf.org> writes:

> Should be bf695b937e.

Hmm - I still have a problem.  I did git clean -xf then rebuilt and
I still get this:

Debugger entered--Lisp error: (error "Cannot find suitable directory for output in ‘nati...")
  error("Cannot find suitable directory for output in `nati...")
  comp-trampoline-compile(read-string)
  comp-subr-trampoline-install(read-string)
  advice--add-function(:around (#f(compiled-function () #<bytecode 0x3647c019df7e91>) . #f(compiled-function (gv--val) #<bytecode 0x85c60bbba7cb3c2>)) my-read-string--default-in-prompt-around-ad nil)
  advice-add(read-string :around my-read-string--default-in-prompt-around-ad)
  load-with-code-conversion("/home/micha/gnu-emacs/.gnu-emacs.el" "/home/micha/gnu-emacs/.gnu-emacs.el" nil nil)
  load("~/gnu-emacs/.gnu-emacs")
  load-with-code-conversion("/home/micha/.emacs" "/home/micha/.emacs" t t)
  load("~/.emacs" noerror nomessage)
  startup--load-user-init-file(#f(compiled-function () #<bytecode 0x14ae77e413cd36de>) #f(compiled-function () #<bytecode -0x1f3c6feddc0c6975>) t)
  command-line()
  normal-top-level()

Is there anything else to clean up?

Michael.





  reply	other threads:[~2022-01-29 17:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28  6:42 bug#53596: 29.0.50; comp-trampoline-compile: Cannot find suitable directory for output in `native-comp-eln-load-path' Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28  9:50 ` Andrea Corallo
2022-01-28  9:52   ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28  9:57     ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:06     ` Andrea Corallo
2022-01-28 10:09       ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:10         ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:22           ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 10:32             ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 13:00               ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 13:33                 ` Andrea Corallo
2022-01-28 13:49                   ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 13:55                     ` Andrea Corallo
2022-01-28 14:03                     ` Lars Ingebrigtsen
2022-01-28 14:18                       ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 14:27                         ` Lars Ingebrigtsen
2022-01-28 16:53                           ` Manuel Uberti via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-28 19:07                           ` Michael Heerdegen
2022-01-29  7:41                             ` Andrea Corallo
2022-01-29 17:36                               ` Michael Heerdegen [this message]
2022-01-29 17:55                                 ` Eli Zaretskii
2022-01-30  1:26                                   ` Michael Heerdegen
2022-01-30  6:45                                     ` Eli Zaretskii

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=87fsp6zbog.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=53596@debbugs.gnu.org \
    --cc=akrl@sdf.org \
    --cc=larsi@gnus.org \
    --cc=manuel.uberti@inventati.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).