unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark Kennedy <mark.t.kennedy@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55211@debbugs.gnu.org
Subject: bug#55211: 29.0.50; bad package/native comp interaction
Date: Mon, 2 May 2022 16:43:44 -0400	[thread overview]
Message-ID: <CANru7VEVPeo-GR-RBZ5Jxh8Gwa0k-MRGPMU2JiXu7JX6vzHHCA@mail.gmail.com> (raw)
In-Reply-To: <8735htc6wh.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]

and now the error has gone away for me as well.  something cached in
~/.emacs.d must have been the source of the problem.  sorry for the fire
drill.
/mark

On Sun, May 1, 2022 at 4:52 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Mark Kennedy <mark.t.kennedy@gmail.com> writes:
>
> > this is one of those "too complicated for a -Q recipe" stories.
> >
> > running "package-list-packages" with a native-comp emacs binary
> > fails with a "too many open files" message.  if lsof is used to examine
> > the emacs process, there are hundreds of read-only file descriptors
> bound to
> > "tramp-archive.elc".  if the same .emacs.d tree is run against an emacs
> > binary built *without* native compilation, it works correctly.
>
> [...]
>
> > System Description: Fedora Linux 35 (Workstation Edition)
>
> I tried that just now (nativecomp on Debian/bookworm), and I didn't get
> any errors.
>
> Are you saying you don't get the error if you say `M-x
> package-list-packages' in an "emacs -Q", but you get it with a non-Q
> Emacs?
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1733 bytes --]

  reply	other threads:[~2022-05-02 20:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-01 20:48 bug#55211: 29.0.50; bad package/native comp interaction Mark Kennedy
2022-05-01 20:52 ` Lars Ingebrigtsen
2022-05-02 20:43   ` Mark Kennedy [this message]
2022-05-03  9:07     ` 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=CANru7VEVPeo-GR-RBZ5Jxh8Gwa0k-MRGPMU2JiXu7JX6vzHHCA@mail.gmail.com \
    --to=mark.t.kennedy@gmail.com \
    --cc=55211@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).