← Back to team overview

linux-traipu team mailing list archive

[Bug 735850] Re: --disable-rpath seems broken in 2011.03.13

 

** Summary changed:

- Buy Ambien Online and Know More About its Effects
+ --disable-rpath seems broken in 2011.03.13

** Description changed:

  Building RPMs bails at the end due to rpaths... even though '--disable-
  rpath' is passed to configure.
  
  + /usr/lib/rpm/check-rpaths
  *******************************************************************************
- * https://yourrxpills.com/product-category/buy-ambien-online/
+ *
  * 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.
+ * 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
+ * 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
+ * $ 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
+ * $ RPM_BUILD_ROOT=<top-dir> /usr/lib/rpm/check-rpaths
  *
  *******************************************************************************
- ERROR   0001: file '/usr/lib64/drizzle7/libslave_plugin.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/bin/drizzleslap' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/bin/drizzleadmin' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/bin/drizzledump' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/bin/drizzle' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/bin/drizzleimport' contains a standard rpath '/usr/lib64' in [/usr/lib64]
- ERROR   0001: file '/usr/sbin/drizzled7' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/lib64/drizzle7/libslave_plugin.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/bin/drizzleslap' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/bin/drizzleadmin' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/bin/drizzledump' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/bin/drizzle' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/bin/drizzleimport' contains a standard rpath '/usr/lib64' in [/usr/lib64]
+ ERROR 0001: file '/usr/sbin/drizzled7' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  error: Bad exit status from /var/tmp/rpm-tmp.0GEVOR (%install)

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/735850

Title:
  --disable-rpath seems broken in 2011.03.13

Status in Drizzle:
  Confirmed

Bug description:
  Building RPMs bails at the end due to rpaths... even though
  '--disable-rpath' is passed to configure.

  + /usr/lib/rpm/check-rpaths
  *******************************************************************************
  *
  * 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/lib64/drizzle7/libslave_plugin.so' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/bin/drizzleslap' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/bin/drizzleadmin' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/bin/drizzledump' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/bin/drizzle' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/bin/drizzleimport' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  ERROR 0001: file '/usr/sbin/drizzled7' contains a standard rpath '/usr/lib64' in [/usr/lib64]
  error: Bad exit status from /var/tmp/rpm-tmp.0GEVOR (%install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/735850/+subscriptions