From: Matt Simmons <simmonmt@cs.purdue.edu>
Cc: ding-patches@gnus.org
Subject: Re: Gnus v5.4.47 is released
Date: 27 Apr 1997 12:57:54 -0500 [thread overview]
Message-ID: <yuq4tcsmjq5.fsf@borg14.cs.purdue.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 27 Apr 1997 12:37:34 +0200
Am I the only one who had 5.4.47 blow up on make? On anything past
earcon (inclusive), it complains that it can't find various gnus-*
files (earcon complains about gnus-ems). A truss reveals that XEmacs
is finding the .el files, but when it tries to open them, it gets an
EMFILE. I next tried upping the maximum file descriptors to 128, and
got the same behavior. At 1024, XEmacs bails out, complaining that
the nesting level is too deep.
On a side note, when I try to access nndoc groups (with any command),
I get "Wrong type argument: listp, all". Has anybody else seen this
before?
Thanks
next prev parent reply other threads:[~1997-04-27 17:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-04-27 10:37 Lars Magne Ingebrigtsen
1997-04-27 17:57 ` Matt Simmons [this message]
1997-04-27 18:59 ` Steven L Baur
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=yuq4tcsmjq5.fsf@borg14.cs.purdue.edu \
--to=simmonmt@cs.purdue.edu \
--cc=ding-patches@gnus.org \
--cc=simmonmt@acm.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.
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 NNTP newsgroup(s).