Bug 672820

Summary:	www-client/chromium-71.0.3578.80[component-build] - src_install(): ERROR: ... failed: Aborting due to serious QA concerns with RUNPATH/RPATH
Product:	Gentoo Linux	Reporter:	Ole Langbehn <neurolabs.de>
Component:	Current packages	Assignee:	Chromium Project <chromium>
Status:	RESOLVED WONTFIX
Severity:	normal	CC:	arthur
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	tail of build log output of emerge --info split build log part 1 split build log part 2 split build log part 3 split build log part 4 split build log part 5 split build log part 6

Description Ole Langbehn 2018-12-09 14:33:39 UTC

from the build log:

scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN/.' in /var/tmp/portage/www-client/chromium-71.0.3578.80/image/usr/lib64/chromium-browser/chrome-sandbox with mode set of 4755
scanelf: rpath_security_checks(): Security problem with DT_RPATH='$ORIGIN/.' in /var/tmp/portage/www-client/chromium-71.0.3578.80/image/usr/lib64/chromium-browser/chrome-sandbox with mode set of 4755

 * 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.
 * $ORIGIN/. /var/tmp/portage/www-client/chromium-71.0.3578.80/image/usr/lib64/chromium-browser/chrome-sandbox

Comment 1 Ole Langbehn 2018-12-09 14:36:41 UTC

Created attachment 557406 [details]
tail of build log

Comment 2 Ole Langbehn 2018-12-09 14:37:36 UTC

Created attachment 557408 [details]
output of emerge --info

Comment 3 Ole Langbehn 2018-12-09 14:59:22 UTC

This only happens when enabling the USE flag component-build

Comment 4 Ole Langbehn 2018-12-09 15:01:01 UTC

Found a discussion on the chromium bugtracker where this issue was discussed before: https://bugs.chromium.org/p/chromium/issues/detail?id=608596

Comment 5 Jeroen Roovers (RETIRED) gentoo-dev

2018-12-09 15:30:10 UTC

Comment on attachment 557406 [details]
tail of build log

Please attach the entire build log to this bug report. If you think you cannot do that, then consider using file compression

xz build.log

and upload build.log.xz

If that still does not fit, split up the file into chunks and upload those.

Comment 6 Ole Langbehn 2018-12-09 16:02:00 UTC

Created attachment 557412 [details]
split build log part 1

Comment 7 Ole Langbehn 2018-12-09 16:02:25 UTC

Created attachment 557414 [details]
split build log part 2

Comment 8 Ole Langbehn 2018-12-09 16:02:42 UTC

Created attachment 557416 [details]
split build log part 3

Comment 9 Ole Langbehn 2018-12-09 16:03:00 UTC

Created attachment 557418 [details]
split build log part 4

Comment 10 Ole Langbehn 2018-12-09 16:03:17 UTC

Created attachment 557420 [details]
split build log part 5

Comment 11 Ole Langbehn 2018-12-09 16:03:36 UTC

Created attachment 557422 [details]
split build log part 6

Comment 12 Ole Langbehn 2018-12-09 16:04:53 UTC

The split build log can simply be cat'ed together to a gz archive containing the build log.

Comment 13 Ole Langbehn 2019-12-30 15:00:41 UTC

does not happen with current builds of chromium