Re: [Ltib] LTIB build failure (rpath)

[Stuart Hughes]

Hi Jonathan,

I'm just off on vacation in a moment, but take a look at this:
http://www.linuxquestions.org/questions/fedora-35/warning-check-rpaths-detected-a-broken-rpath-and-will-cause-rpmbuild-to-fail-606748/

The best thing would be to find a "kind" way to disable this check.  For
example I did a similar thing in rpm-fs.spec when I added:

export NO_BRP_STALE_LINK_ERROR=yes

Take a look at /usr/lib/rpm/check-rpaths (and the other bits of the host
rpm) and see if there's a way of disabling this check.  

BTW: I didn't see an attachment.

Regards, Stuart

On Tue, 2007-12-18 at 12:21 -0500, Jonathan S. Shapiro wrote:
> 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 home page: http://bitshrine.org
> 
> Ltib mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/ltib