From: Eli Zaretskii <eliz@gnu.org>
To: Manuel Uberti <manuel.uberti@inventati.org>,
Andrea Corallo <akrl@sdf.org>
Cc: 49118@debbugs.gnu.org
Subject: bug#49118: 28.0.50; Error: File error Opening output file
Date: Sat, 19 Jun 2021 17:55:39 +0300 [thread overview]
Message-ID: <838s35x5sk.fsf@gnu.org> (raw)
In-Reply-To: <f3931d72-8020-27d5-8d67-e36c738797c8@inventati.org> (message from Manuel Uberti on Sat, 19 Jun 2021 16:34:41 +0200)
> Cc: 49118@debbugs.gnu.org
> From: Manuel Uberti <manuel.uberti@inventati.org>
> Date: Sat, 19 Jun 2021 16:34:41 +0200
>
> On 19/06/21 16:32, Eli Zaretskii wrote:
> > What happens if you invoke the native-compilation like this:
> >
> > $ emacs -batch -l comp -f batch-native-compile /usr/local/share/emacs/28.0.50/lisp/time.el.gz
> >
> > Does this also fail, and if so, what error message(s) do you see?
>
> This is what I get:
>
> manuel@hathaway:~$ emacs -batch -l comp -f batch-native-compile
> /usr/local/share/emacs/28.0.50/lisp/time.el.gz
> uncompressing time.el.gz...
> uncompressing time.el.gz...done
> Debugger entered--Lisp error: (file-error
> "/usr/local/share/emacs/28.0.50/lisp/time.el.gz" "Opening output file" "Cannot
> overwrite file" "/usr/local/share/emacs/28.0.50/lisp/time.elc")
> signal(file-error ("/usr/local/share/emacs/28.0.50/lisp/time.el.gz" "Opening
> output file" "Cannot overwrite file"
> "/usr/local/share/emacs/28.0.50/lisp/time.elc"))
> comp--native-compile("/usr/local/share/emacs/28.0.50/lisp/time.el.gz")
> batch-native-compile()
> command-line-1(("-l" "comp" "-f" "batch-native-compile"
> "/usr/local/share/emacs/28.0.50/lisp/time.el.gz"))
> command-line()
> normal-top-level()
Thanks.
Andrea, this means bug#48978 was not entirely fixed: we are still
trying to write the *.elc files when native-compiling. Your last
change prevented Emacs from trying to create a temporary file under
/usr/share/emacs, but it didn't prevent the rest of byte-compile-file
from trying to overwrite the original .elc file, which here causes us
to signal an error. We need to avoid writing the .elc file entirely
in this case, I think.
next prev parent reply other threads:[~2021-06-19 14:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-19 14:21 bug#49118: 28.0.50; Error: File error Opening output file Manuel Uberti
2021-06-19 14:32 ` Eli Zaretskii
2021-06-19 14:34 ` Manuel Uberti
2021-06-19 14:55 ` Eli Zaretskii [this message]
2021-06-21 10:21 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-06-21 10:33 ` Manuel Uberti
2021-06-21 12:19 ` Eli Zaretskii
2021-06-21 12:34 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838s35x5sk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=49118@debbugs.gnu.org \
--cc=akrl@sdf.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.