Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!hellgate.utah.edu!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: Can't assign requested address
Message-ID: <4601@helios.ee.lbl.gov>
X-Local-Date: 10 Jan 90 11:59:40 PST
Date: 10 Jan 90 19:59:40 GMT
References: <9001101337.AA02509@expire.lcs.mit.edu> <1990Jan9.224238.28795@decatl.dec.com>
Sender: usenet@helios.ee.lbl.gov
Reply-To: envbvs@epb2.lbl.gov (Brian V. Smith)
Organization: Lbl
Lines: 24

In article <9001101337.AA02509@expire.lcs.mit.edu>, rws@EXPO.LCS.MIT.EDU
(Bob Scheifler) writes:
< 
<     Getting interface configuration: Can't assign requested address
< 
< (Aren't you reading this list?)  Are you sure you had run gcc's
< "fixincludes" before compiling the system?  If not, then all
< ioctl() calls are mis-compiled.

I have been reading this list and I thought I had run fixincludes.
However, to be sure, I recompiled all the routines that had ioctls in them and
then some (including lib/X/XConnDis.c) using cc, but that didn't help.

Listen to this, though:  Now that I have the R4 server AND R4 clients 
working together (using all cc), when I try to start an R3 client on the
R4 server, it gets the "Can't assign requested address" error.

How could this possibly have anything to do with bad ioctls?
Or does it mean that both the R3 server and clients were broken in the
same way so that they worked together OK?
_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.