Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!swbatl!adams From: adams@swbatl.sbc.com (Tom Adams - 235-7459) Newsgroups: comp.sys.pyramid Subject: Re: xterm /dev/tty fix Message-ID: <1990Sep11.130000.795@swbatl.sbc.com> Date: 11 Sep 90 13:00:00 GMT References: <1990Sep9.032703.27619@swbatl.sbc.com> <607@bohra.cpg.oz> Reply-To: adams@swbatl.UUCP (Tom Adams - 235-7459) Organization: Southwestern Bell Lines: 18 In article <607@bohra.cpg.oz> ejp@bohra.cpg.oz (Esmond Pitt) writes: >In article karl_kleinpaste@cis.ohio-state.edu writes: >*Details for porting X11R4 to the att universe are available from me on >request. If there's enough interest, I will post here. I'm curious about the more general problem of resolving references to network facilities when code is compiled in the AT&T universe. It's easy enough when all the references are in a seperate source module, but when someone mixes networking code with AT&T specific stuff in the same source module it's a real pain to get going. Has anyone been able to pull all the networking stuff into a seperate object library? I've started a few times and gotten hung up at different places. This comes up regularly here when moving code from Sys V machines with added networking facilities. -- uunet!swbatl!adams or adams@swbatl.sbc.com Tom Adams: 314-235-7459: Southwestern Bell Telephone Advanced Technology Lab BOOKS WANTED: pre-1930 radio, electrical & scientific topics