[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Ltib] LTIB build failure (rpath)
From: |
Jonathan S. Shapiro |
Subject: |
[Ltib] LTIB build failure (rpath) |
Date: |
Tue, 18 Dec 2007 12:21:43 -0500 |
I'm trying to install ltib on a Fedora-8 machine. The install fails, and
the log file shows that check-rpath reported an invalid path. Many
errors. A typical one is:
> ERROR 0002: file '/opt/ltib/usr/lib/rpm/rpmq' contains an invalid rpath
> '/opt/ltib/usr/lib' in [/opt/ltib/usr/lib]
This smells like /opt/ltib/ us completely unknown to check-rpaths. There
is also a longer diagnostic in the log file, which I am attaching below.
I'm sure this is a known issue. Is there a known workaround? If so,
should it perhaps be added to the FAQ?
Thanks
shap
> + /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
> *
> *******************************************************************************
- [Ltib] LTIB build failure (rpath),
Jonathan S. Shapiro <=