gcc wrapper aborts when /tmp/sysroot_wrapper.error* is not accessible (e.g. owned by root) |
|||
Issue descriptionTraceback (most recent call last): File "/usr/lib64/python2.7/logging/handlers.py", line 77, in emit self.doRollover() File "/usr/lib64/python2.7/logging/handlers.py", line 139, in doRollover os.remove(dfn) OSError: [Errno 1] Operation not permitted: '/tmp/sysroot_wrapper.error.1' Logged from file arm-none-eabi-gcc, line 197 Reproduction steps: 0. cd to src/platform/ec 1. Run make BOARD=nami and terminate build in the middle 2. Run make BOARD=nami again Expected: No error messages. Additional Info: Removing sysroot_wrapper.error.1 manually resolves the issue.
,
Jul 18
I personally think that we should simply get rid of the logging code when SYSROOT is not set. https://cs.corp.google.com/chromeos_public/src/third_party/chromiumos-overlay/sys-devel/gcc/files/sysroot_wrapper.body?l=347
,
Jul 18
,
Jul 19
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/429b84e9da4dc78e59301bbd183b18f2a1a22bc7 commit 429b84e9da4dc78e59301bbd183b18f2a1a22bc7 Author: Manoj Gupta <manojgupta@google.com> Date: Thu Jul 19 01:19:30 2018 compiler wrapper: Drop logging code if SYSROOT is not set. This logging causes problems occasioanlly and no one is looking at these logs anyway. BUG= chromium:865111 TEST=No more logging errors if SYSROOT is not set. Change-Id: I2ef3e38e8d5c48fc899fc9c6678acbc1a92c0f45 Reviewed-on: https://chromium-review.googlesource.com/1142301 Tested-by: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Yunlian Jiang <yunlian@chromium.org> [modify] https://crrev.com/429b84e9da4dc78e59301bbd183b18f2a1a22bc7/sys-devel/gcc/files/sysroot_wrapper.body [rename] https://crrev.com/429b84e9da4dc78e59301bbd183b18f2a1a22bc7/sys-devel/gcc/gcc-4.9.2-r193.ebuild
,
Jul 23
|
|||
►
Sign in to add a comment |
|||
Comment 1 by vapier@chromium.org
, Jul 18