Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 645902 - cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4 contains insecure RUNPATHs
Summary: cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4 contains insecure RUNPATHs
Status: RESOLVED DUPLICATE of bug 582524
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-27 18:17 UTC by Peter
Modified: 2018-01-27 18:30 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge --info output (emerge_info.log,5.13 KB, text/plain)
2018-01-27 18:17 UTC, Peter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter 2018-01-27 18:17:33 UTC
Created attachment 516914 [details]
emerge --info output

I've recently emerged the gcc 5.4.0 package for the ARM crosscompiler toolchain and it ended giving the following warning:

>>> Completed installing gcc-5.4.0-r4 into /tmp/portage/cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4/image/

 * Final size of build directory: 1418852 KiB (  1.3 GiB)
 * Final size of installed tree:   107520 KiB (105.0 MiB)

Auto fixing rpaths for /tmp/portage/cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4/image/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/5.4.0/libstdc++.so.6.0.21

 * QA Notice: The following files contain insecure RUNPATHs
 *  Please file a bug about this at https://bugs.gentoo.org/
 *  with the maintainer of the package.
 *   /tmp/portage/cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4/image/usr/lib/gcc/armv7a-hardfloat-linux-gnueabi/5.4.0/libstdc++.so.6.0.21
 *     RPATH: /tmp/portage/cross-armv7a-hardfloat-linux-gnueabi/gcc-5.4.0-r4/work/build/armv7a-hardfloat-linux-gnueabi/libstdc++-v3/../libvtv/.libs
 *
Comment 1 Sergei Trofimovich (RETIRED) gentoo-dev 2018-01-27 18:30:23 UTC

*** This bug has been marked as a duplicate of bug 582524 ***