Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!aplcen!samsung!usc!henry.jpl.nasa.gov!elroy.jpl.nasa.gov!gryphon!turnkey!jackv From: jackv@turnkey.gryphon.COM (Jack F. Vogel) Newsgroups: comp.windows.x Subject: Re: Questions on setup on ISC's X11 Dev Message-ID: <6405@turnkey.gryphon.COM> Date: 1 Jan 90 22:16:16 GMT References: <8912291842.AA12534@decwrl.dec.com> Reply-To: jackv@turnkey.gryphon.COM Organization: Turnkey Computer Consultants, Westchester, CA Lines: 26 In article <8912291842.AA12534@decwrl.dec.com> paine@fungus.dec.com (Willy Paine) writes: >My questions are: >Should I make separate header file to resolve X11 header problem or >modifying inside X11 header files (Vos.h etc)? >How can I overcome the problem with many unresolved external from ISC's >own X11 library for my future X11 development? How is anyone supposed to help you when you leave out essential details like what the unresolved externals were or what the header files that were not found were???? All I can say without these details is that I have been using the ISC X development package without these problems. My guess is that the unresolved externals one might get would come from the BSD networking library stuff, to resolve that include -linet in your linker flags (this assumes you have /usr/lib/libinet.a installed, I forget what package it is in). The other type of problem I have had involved some client code that used header files normally in the libX source directory that ISC did not distribute in . I don't recall what they were but if you have the X distribution around it shouldn't be too hard to figure out. Good Luck, -- Jack F. Vogel jackv@seas.ucla.edu AIX Technical Support - or - Locus Computing Corp. jackv@ifs.umich.edu