Path: utzoo!utgpu!watmath!iuvax!mailrus!cornell!batcomputer!hurf From: hurf@batcomputer.tn.cornell.edu (Hurf Sheldon) Newsgroups: comp.unix.ultrix Subject: DS3100 questions - which Endian? (Compiling NCAR2.0) Keywords: NCAR endian big little mips fortran cc TeX Message-ID: <8588@batcomputer.tn.cornell.edu> Date: 9 Aug 89 03:01:00 GMT Reply-To: hurf@tcgould.tn.cornell.edu (Hurf Sheldon) Organization: Cornell Theory Center, Cornell University, Ithaca NY Lines: 29 1: Would someone take the time to straighten me out on the DecStation 3100 byte ordering and it's ramifications? I am trying to compile some code (NCAR2.0) that is dependent on some byte ordering code depending on the processor. Generally vax vs the rest of the world. I thought the 3100 built with the -EL flag looked like a vax from a byte perspective but using a -Dvax at as a CDEFINE makes for other errors. I have found in one set of display routines (plt) ensuring the vax byte ordering routines were included got me half way there. If someone is familiar with the specific problem of NCAR: the .cgm files from the mips display ok on a vax. Forcing plt to use the vax_swap.h code let it open the cgm file without a record length error but the plots are gibberish so I suspect the information is being translated by cgmtrans or trnspprt incorrectly as the vax confirms the cgm file is correct. 2: TeX on the mips? Has anyone tried ctex? - Thanks, -- Hurf Sheldon Network: hurf@ionvax.tn.cornell.edu Lab of Plasma Studies Bitnet: hurf@CRNLION 369 Upson Hall, Cornell University, Ithaca, N.Y. 14853 ph:607 255 7267 I got a job in science; I bought a Porsche; Now, everyone takes me seriously.