Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!shelby!bloom-beacon!mgm.mit.edu!wolfgang
From: wolfgang@mgm.mit.edu (Wolfgang Rupprecht)
Newsgroups: gnu.emacs.bug
Subject: Re: 386/ix: X support and shared libraries
Message-ID: <15913@bloom-beacon.MIT.EDU>
Date: 15 Nov 89 01:56:24 GMT
References: <12551@cit-vax.Caltech.Edu>
Sender: daemon@bloom-beacon.MIT.EDU
Reply-To: wolfgang@BBN.COM (Wolfgang Rupprecht)
Distribution: gnu
Organization: Freelance Software Consultant, Washington DC.
Lines: 27

In article <12551@cit-vax.Caltech.Edu> tim@cit-vax.UUCP (Timothy L. Kay) writes:
>The only symptom I find is that xemacs doesn't work under X windows,
>but temacs does.  I am running Interactive 386/ix on a 386 clone.

Yes, I can confirm this problem.  Vitals:
	ATT 6386  (PC clone)
	ATT SysV
	/bin/cc
	ISC "port" X11r3
	Interlan Network code

Firstly Interlan and ISC need to get their acts together.  The two
binary-only "commercial quality" packages don't work well enough to
even run a normal X program over the network!
	
Secondly even on a local system, xemacs dumps core in (emacs) select().
The problem is that emacs select gets called with timeout_pointer == 0
from XKeyReadable() [quoted from memory].  Hacking emacs select to
understand null-pointer timeouts (via treating it as *timeout ==
10000) causes an infinate-polling loop from XkeyReadable().

I have no ISC sources, so I am tempted to punt.  Lets Stamp out this
binary bullshit!  

-wolfgang
Wolfgang Rupprecht	ARPA:  wolfgang@mgm.mit.edu (IP 18.82.0.114)
TEL: (703) 768-2640	UUCP:  mit-eddie!mgm.mit.edu!wolfgang