New issue
Advanced search Search tips

Issue 894723 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 19
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug
Build-Toolchain



Sign in to add a comment

random stXXXXXX dirs installed in /usr/lib/ with objects in them

Project Member Reported by vapier@chromium.org, Oct 12

Issue description

there seems to be something funky going on.  my guess is it's related to stripping of static archives.  haven't investigated further than these dirs shouldn't exist in the first place.

$ qfile /usr/lib64/st??????
chromeos-base/libbrillo (/usr/lib64/stidOPVN)
chromeos-base/libbrillo (/usr/lib64/stoiixn4)
chromeos-base/google-breakpad (/usr/lib64/st62SXqe)
chromeos-base/google-breakpad (/usr/lib64/stnRocdw)

lots more under /usr/lib64/clang/8.0.0/lib/linux/

$ ls /usr/lib64/stnRocdw
ls: cannot open directory '/usr/lib64/stnRocdw': Permission denied
$ sudo ls /usr/lib64/stnRocdw
basic_code_modules.o  basic_source_line_resolver.o  call_stack.o  cfi_frame_info.o  convert_old_arm64_context.o  disassembler_x86.o  dump_context.o
 
 Issue 904234  has been merged into this issue.
Owner: manojgupta@chromium.org
Most likely caused by new clang option -faddrsig turned on as default in upstream.

The use of -faddrsig is onloy for -icf=.. options which we use only for Chrome.
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 16

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/3c524e9324008aecc0e80d10c665977fb83a3f9a

commit 3c524e9324008aecc0e80d10c665977fb83a3f9a
Author: Manoj Gupta <manojgupta@google.com>
Date: Fri Nov 16 23:10:49 2018

llvm: Disable -faddrsig option for host builds.

clang upstream now enables -faddrsig option as default
which produces sections that binutils strip does not understand.
This causes strip to fail for some bjects and leave a bunch of stray
object files installed to the chroot.

This option is to efficiently enable "-icf=all" linker option but
there is no use of "-icf=all" in the host builds. So let's drop this
option from the host wrapper for now.

Should also evaluate dropping this from target builds except chrome
but .o files are automatically masked from being installed on image
so this isn't a problem yet for target packages.

BUG= chromium:894723 
TEST=sudo emerge libbrillo and checked that no .o files are installed.

Change-Id: I2f0ab80eeeaa6f405ad5bbda6e3c34e33e00cc8c
Reviewed-on: https://chromium-review.googlesource.com/1338498
Commit-Ready: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Caroline Tice <cmtice@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/3c524e9324008aecc0e80d10c665977fb83a3f9a/sys-devel/llvm/files/clang_host_wrapper.body
[rename] https://crrev.com/3c524e9324008aecc0e80d10c665977fb83a3f9a/sys-devel/llvm/llvm-8.0_pre339409_p20180926-r6.ebuild

Status: Verified (was: Untriaged)

Sign in to add a comment