Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!sgi!ciemo@bananapc.wpd.sgi.com
From: ciemo@bananapc.wpd.sgi.com (Dave Ciemiewicz)
Newsgroups: comp.sys.sgi
Subject: Re: 4d 20-> 4d80gt porting bug
Summary: Graphics binary compatibility requires shared libraries
Keywords: Intra 4D family port, 4d binary compatability
Message-ID: <41032@sgi.sgi.com>
Date: 26 Aug 89 03:25:06 GMT
References: <8710@batcomputer.tn.cornell.edu>
Sender: ciemo@bananapc.wpd.sgi.com
Organization: Silicon Graphics, Inc., Mountain View, CA
Lines: 26

In article <8710@batcomputer.tn.cornell.edu>, piplani@batcomputer.tn.cornell.edu (Michael Piplani) writes:
> I wrote a simple graphics driver for a program of ours on a 4d/20- personal
> iris.  Our program worked fine on all our test cases.  We shipped a binary 
> to someone with a 4d/80 gt with alpha blending. When it starts up it
> dies with this message: "Unable to map FIFO no such device"
> 
> I thought there was binary compatability across the 4d family.
> 
> Any ideas?  It just occured to me that we didn't use the shared 
> graphics libraries (just linked with good ole' -Zg), could this be the
> problem?
> 

It is definitely the problem.  You should be linking with the shared GL.
-Zg is maintained for backward compatibility.  Instead, link your program
with "-lgl_s".  Besides providing a binary compatibility, linking to the
shared library will also reduce the size of your executable since it won't
have its own copies of the GL routines.

--
-------------------------------------------------------------------------------
			Cosmo Ciemo, Silicon Valley Dude

I was traipsing through the fields of my mind when I stepped in something that
smelled rather ripe.
-------------------------------------------------------------------------------