[1459] in Release_7.7_team

home help back first fref pref prev next nref lref last post

Re: more on BioSym problems

daemon@ATHENA.MIT.EDU (Robert A Basch)
Thu Aug 13 23:27:29 1998

To: Alex T Prengel <alexp@MIT.EDU>
Cc: Robert A Basch <rbasch@MIT.EDU>, wdc@MIT.EDU, mbarker@MIT.EDU,
        ghudson@MIT.EDU, release-team@MIT.EDU
In-Reply-To: Your message of "Thu, 13 Aug 1998 18:41:33 EDT."
             <199808132241.SAA17808@merriweather.mit.edu> 
Date: Thu, 13 Aug 1998 23:27:23 EDT
From: Robert A Basch <rbasch@MIT.EDU>

> >> Yeah, I would make sure that the eoe.sw32.gfx subsystem is installed on the
> >> systems that are having problems.
> 
> >OK, I found a problem here.  The installation of this package does the
> >wrong thing in symlink mode
> 
> Do you mean we set it up wrong in the Release?

Essentially, yes.  The longer answer is, the IRIX installation tool (inst)
has a symlink mode, which installs files as symbolic links to the same
file in a given tree; we use this to install most packages, with files
linked to /os.  Thus, for example, /usr/lib32/libGLcore.so is a symlink
to /os/usr/lib32/libGLcore.so, which, through a couple more symlinks to
relative paths, ends up pointing at the XZ version of the file in the
/os tree, /os/usr/gfx/arch/IP12GR232/libGLcore.so.  (We create the /os
tree such that it contains all of the hardware-specific files needed to
support our various types of machine).

We can fix this by installing the package locally in a patch release;
this requires an update to the install volume.

Bob


home help back first fref pref prev next nref lref last post