bqsy1@vax5.cit.cornell.edu (02/15/91)
We recently built X11R4 on a DECstation 3100 running Ultrix 4.1,
using DEC's cc. Everything went well with no reported compilation or
linking errors. However, we have run into the following problem - we seem
to be unable to run the dx* binaries under X11R4. Any attempt to run these
produces a core dump.
My understanding of DEC's Xserver, and from looking at the
libraries and include files for DEC's X11, is that is an R4 port, without
the extensions. What else did DEC do to its clients to make them not work
under MIT's R4??
I should say that we've run MIT clients under the DEC Xserver with
no problem. Even clients that require the shape extension run,though they
default to DEC's Server when opening windows and creating buttons and
widgets.
Any help at all would be appreciated.
Andrew Orndorff
Cornell Information Technologies, Cornell University
Internet: bqsy1@vax5.cit.cornell.edu
Bitnet: bqsy1@crnlvax5klee@wsl.dec.com (Ken Lee) (02/15/91)
In article <1991Feb14.160319.2761@vax5.cit.cornell.edu>, bqsy1@vax5.cit.cornell.edu writes: |> |> We recently built X11R4 on a DECstation 3100 running Ultrix 4.1, |> using DEC's cc. Everything went well with no reported compilation or |> linking errors. However, we have run into the following problem - we seem |> to be unable to run the dx* binaries under X11R4. Any attempt to run these |> produces a core dump. If the clients are reporting that they cannot find certain fonts, then you should install the fonts on your server machine. There are various ways to do this. One easy work around is to install the DEC fonts.alias file. A copy of this is in the contrib directory of expo.lcs.mit.edu. -- Ken Lee DEC Western Software Laboratory, Palo Alto, Calif. Internet: klee@wsl.dec.com uucp: uunet!decwrl!klee
iglesias@draco.acs.uci.edu (Mike Iglesias) (02/15/91)
In article <1991Feb14.160319.2761@vax5.cit.cornell.edu> bqsy1@vax5.cit.cornell.edu writes: > > We recently built X11R4 on a DECstation 3100 running Ultrix 4.1, >using DEC's cc. Everything went well with no reported compilation or >linking errors. However, we have run into the following problem - we seem >to be unable to run the dx* binaries under X11R4. Any attempt to run these >produces a core dump. If you've pointed /usr/lib/X11 at the X11R4 copy, you're missing the app-defaults files, the files in /usr/lib/X11/eu, and the files in /usr/lib/X11/uid from the DEC distribution. Without some subset (or all) of those files, the dx clients core dump. You'll have to mix the DEC files in with the X11R4 files to make the dx clients work. > My understanding of DEC's Xserver, and from looking at the >libraries and include files for DEC's X11, is that is an R4 port, without >the extensions. What else did DEC do to its clients to make them not work >under MIT's R4?? No, DEC's server is X11R3, although Ultrix 4.2 is rumored to have an X11R4 server. Mike Iglesias University of California, Irvine Internet: iglesias@draco.acs.uci.edu BITNET: iglesias@uci uucp: ...!ucbvax!ucivax!iglesias
jg@quabbin.crl.dec.com (Jim Gettys) (02/15/91)
In article <1991Feb14.160319.2761@vax5.cit.cornell.edu> bqsy1@vax5.cit.cornell.edu writes: > > We recently built X11R4 on a DECstation 3100 running Ultrix 4.1, >using DEC's cc. Everything went well with no reported compilation or >linking errors. However, we have run into the following problem - we seem >to be unable to run the dx* binaries under X11R4. Any attempt to run these >produces a core dump. > My understanding of DEC's Xserver, and from looking at the >libraries and include files for DEC's X11, is that is an R4 port, without >the extensions. What else did DEC do to its clients to make them not work >under MIT's R4?? > I should say that we've run MIT clients under the DEC Xserver with >no problem. Even clients that require the shape extension run,though they >default to DEC's Server when opening windows and creating buttons and >widgets. > Any help at all would be appreciated. If you look at the frequently asked questions list posted periodically in comp.windows.x, you'd find a reference to the fact the DECwindows clients depend on fonts you may not have. If you install an appropriate fonts.alias file you should be all set. Pointers to the file are in the FAQ list, or you can grovel around gatekeeper.dec.com's anonymous ftp area to find it (I don't remember the file name off the top of my head. Also note you should do an "xset bc" to enable bug compatibitity on an R4 server; if you happen to be using older DECwindows versions, you may run into problems if you don't (the more recent the DECwindows release, the less likely this may be necessary. This is true actually when running any client from before R4; a number of bugs were fixed in R4 that may cause buggy older clients to break. - Jim Gettys -- Digital Equipment Corporation Cambridge Research Laboratory
D. Allen [CGL]) (02/16/91)
In article <1991Feb14.160319.2761@vax5.cit.cornell.edu> bqsy1@vax5.cit.cornell.edu writes: > We recently built X11R4 on a DECstation 3100 running Ultrix 4.1, >using DEC's cc. Everything went well with no reported compilation or >linking errors. However, we have run into the following problem - we seem >to be unable to run the dx* binaries under X11R4. Any attempt to run these >produces a core dump. The DEC applications don't behave well if they can't find their fonts. Some programmer probably didn't check the return codes on the font open calls, so they core dump. Probably the same person who programmed Ultrix uucico and uux :-). Try that font alias file that maps DEC font names to MIT font names and see if you get farther. -- -IAN! (Ian! D. Allen) idallen@watcgl.uwaterloo.ca idallen@watcgl.waterloo.edu [129.97.128.64] Computer Graphics Lab/University of Waterloo/Ontario/Canada