unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrew Whatson <whatson@gmail.com>
To: Andrea Corallo <akrl@sdf.org>
Cc: 43858@debbugs.gnu.org
Subject: bug#43858: 28.0.50; [feature/native-comp] Missing eln cache not created
Date: Fri, 9 Oct 2020 14:47:40 +1000	[thread overview]
Message-ID: <CAPE069euV-+99szqOaW3Uy6Ha0Ao3XbSESQH9iJzMGXX+7i4GQ@mail.gmail.com> (raw)
In-Reply-To: <xjftuv5qi3i.fsf@sdf.org>

Hi Andrea,

Thanks, yes, that fixed the main case where the missing directory
wasn't created.  While testing it, I've found another one in subr
trampoline creation; patch submitted as #43875.

Cheers!

On Thu, 8 Oct 2020 at 17:42, Andrea Corallo <akrl@sdf.org> wrote:
>
> Andrew Whatson <whatson@gmail.com> writes:
>
> > After removing ~/.emacs.d/eln-cache, running "emacs -q" starts up with
> > the error "native-compile-async: Wrong type argument: stringp, nil".
> > This is caused by `comp-el-to-eln-filename' returning nil due to no
> > writeable eln cache directory being found.
> >
> > I think we should attempt to create the cache directories if they're
> > missing, and have a better error if there is *really* no writeable
> > cache directory.
>
> Hi Andrew,
>
> agree, that's acutally what we have been doing before I broke it two
> days ago with 4a1bb46260 :)
>
> c3bc348f5e * Fix failure when eln-cache is removed (introduced by 4a1bb46260)
>
> fix this for me. Could you please confirm?
>
> Thanks
>
>   Andrea





  reply	other threads:[~2020-10-09  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08  0:01 bug#43858: 28.0.50; [feature/native-comp] Missing eln cache not created Andrew Whatson
2020-10-08  7:42 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-10-09  4:47   ` Andrew Whatson [this message]
2020-10-09  6:32     ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=CAPE069euV-+99szqOaW3Uy6Ha0Ao3XbSESQH9iJzMGXX+7i4GQ@mail.gmail.com \
    --to=whatson@gmail.com \
    --cc=43858@debbugs.gnu.org \
    --cc=akrl@sdf.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).