Problem with GNUS/Solaris 2.4

Problem with GNUS/Solaris 2.4

Post by A.M. Zanke » Wed, 05 Apr 1995 04:00:00



Can anybody help with a GNUS problem?

I built Xemacs under Solaris 2.4 on a Sparc 5 yesterday. Everything seems
to be working fine apart from GNUS which gives me the following message
whilst reading the active file on our newshost:

Invalid read syntax: "Integer constant overflow in reader", "1932441289",
 10

Has anybody seen anything like this before?

Thanks in advance,

Mike
--

Department of Mathematics and Statistics |
University of Newcastle upon Tyne, UK    | PGP public key available

 
 
 

Problem with GNUS/Solaris 2.4

Post by Anthony Rossi » Wed, 05 Apr 1995 04:00:00




   Can anybody help with a GNUS problem?

   I built Xemacs under Solaris 2.4 on a Sparc 5 yesterday. Everything seems
   to be working fine apart from GNUS which gives me the following message
   whilst reading the active file on our newshost:

   Invalid read syntax: "Integer constant overflow in reader", "1932441289",
    10

   Has anybody seen anything like this before?

Actually, yes.  But I've not figured out how to solve it.  Apparently,
some news group (as per the *nntp* log buffer) has some really,
really, but I mean REALLY weird numbers for keeping track
(i.e. instead of numbers in the hundreds or thousands, it has numbers
as the above).

Since gnus under FSF's emacs works, I use that instead.  

And havn't complained, since I've not really had a chance to figure
out the cause...

-tony

--
Anthony Rossini                  Assistant Professor and General Nuisance
Center for Biostatistics and Epidemiology, Penn State College of Medicine
P.O. Box 850, Hershey, PA 17033-0850  717-531-7178 (w) 717-531-5779 (fax)

http://wishart.biostats.hmc.psu.edu:2000/~arossini/     (slow connection)

 
 
 

1. Is w3 broken on xemacs-19.12 ( Solaris 2.3, with the solaris 2.4 binaries)


|
|Found the following in the w3 info pages.  Wonder if it is the same bug ??
|
|  4. You are running Lucid Emacs 19.x and Solaris 2.x (SunOS 5.x).  For
|     some reason, network processes under Solaris and Lucid Emacs never
|     get a status of `exit' or `closed'.  This causes retrieval of HTTP
|     and gopher pages to hang indefinitely, with Emacs chewing up large
|     amounts of your CPU time.
|
|     NOTE: You do not need to use gateways anymore for this problem.
|
|     With the release of Lucid Emacs 19.10, this problem is fixed if you
|     #define FIX_SOLARIS_W3_BUG somewhere in your config.h or s/*.h
|     configuration file.  This will be in the stock 19.11 release of
|     XEmacs

This was indeed fixed in 19.11, so it can't be the same problem.
It may simply be a bug in W3.  Bill?

ben
--
"... then the day came when the risk to remain tight in a bud was
more painful than the risk it took to blossom." -- Anais Nin

2. setting clock at boot prompt

3. Problem with auto-save.el for Solaris 2.4 Sparcworks

4. Killer Acorn App?

5. Problem with XEmacs 19.13(12) and Solaris 2.4

6. WTB: Mounting Hardware and Bezel for SS5 Floppy

7. X Problem ( maybe due to Solaris 2.4 ? )

8. CTAN

9. Problems with XEmacs 11 on Solaris 2.4

10. 19.11 core dumping under solaris 2.3 and 2.4 (Motif Problem?)

11. problem compiling xemacs 11 (solaris 2.4 X86)

12. Compiling emacs 19.28 problem under Solaris 2.4

13. Problems making GNU emacs (18.57) on Encore Umax SYSV 2.4