TeXlive installation failure, TeXlive update breaks the TeX installation

[Matthew Saltzman]

On Tue, 2010-04-20 at 15:46 -0400, Matthew Saltzman wrote: 
> 
> Also note that evince needs to be removed before the update and rebuilt
> from the SRPM after the update to get the right kpathsea lib version for
> evince-dvi. 

And, irritatingly, evince fails to rebuild (at least for me).  The tail
of the log is (I think I got all the relevant parts...):

        symlinked /usr/lib/debug/usr/lib64/libevdocument.so.1.0.0.debug to /usr/lib/debug/usr/lib64/libevdocument.so.debug
        symlinked /usr/lib/debug/usr/lib64/libevview.so.1.0.0.debug to /usr/lib/debug/usr/lib64/libevview.so.debug
        symlinked /usr/lib/debug/usr/lib64/libevview.so.1.0.0.debug to /usr/lib/debug/usr/lib64/libevview.so.1.debug
        symlinked /usr/lib/debug/usr/lib64/libevdocument.so.1.0.0.debug to /usr/lib/debug/usr/lib64/libevdocument.so.1.debug
        4151 blocks
        + /usr/lib/rpm/check-rpaths /usr/lib/rpm/check-buildroot
        *******************************************************************************
        *
        * WARNING: 'check-rpaths' detected a broken RPATH and will cause 'rpmbuild'
        *          to fail. To ignore these errors, you can set the '$QA_RPATHS'
        *          environment variable which is a bitmask allowing the values
        *          below. The current value of QA_RPATHS is 0x0000.
        *
        *    0x0001 ... standard RPATHs (e.g. /usr/lib); such RPATHs are a minor
        *               issue but are introducing redundant searchpaths without
        *               providing a benefit. They can also cause errors in multilib
        *               environments.
        *    0x0002 ... invalid RPATHs; these are RPATHs which are neither absolute
        *               nor relative filenames and can therefore be a SECURITY risk
        *    0x0004 ... insecure RPATHs; these are relative RPATHs which are a
        *               SECURITY risk
        *    0x0008 ... the special '$ORIGIN' RPATHs are appearing after other
        *               RPATHs; this is just a minor issue but usually unwanted
        *    0x0010 ... the RPATH is empty; there is no reason for such RPATHs
        *               and they cause unneeded work while loading libraries
        *    0x0020 ... an RPATH references '..' of an absolute path; this will break
        *               the functionality when the path before '..' is a symlink
        *          
        *
        * Examples:
        * - to ignore standard and empty RPATHs, execute 'rpmbuild' like
        *   $ QA_RPATHS=$[ 0x0001|0x0010 ] rpmbuild my-package.src.rpm
        * - to check existing files, set $RPM_BUILD_ROOT and execute check-rpaths like
        *   $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
        *  
        *******************************************************************************
        ERROR   0001: file '/usr/bin/evince' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/bin/evince-previewer' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/bin/evince-thumbnailer' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/nautilus/extensions-2.0/libevince-properties-page.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libpsdocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libpdfdocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libdvidocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libtiffdocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libcomicsdocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/evince/1/backends/libdjvudocument.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        ERROR   0001: file '/usr/lib64/libevview.so.1.0.0' contains a standard rpath '/usr/lib64' in [/usr/lib64]
        error: Bad exit status from /var/tmp/rpm-tmp.q3CZUt (%install)
        
        
        RPM build errors:
            user mockbuild does not exist - using root
            group mockbuild does not exist - using root
            user mockbuild does not exist - using root
            group mockbuild does not exist - using root
            user mockbuild does not exist - using root
            group mockbuild does not exist - using root
            user mockbuild does not exist - using root
            group mockbuild does not exist - using root
            Bad exit status from /var/tmp/rpm-tmp.q3CZUt (%install)

Suggestions welcome (in fact, desired desperately!).  This is
mission-critical for me.  Should I use the QRPATHS bitmask?

TIA.
-- 
                Matthew Saltzman

Clemson University Math Sciences
mjs AT clemson DOT edu
http://www.math.clemson.edu/~mjs