|
|
Created:
4 years, 3 months ago by Nico Modified:
4 years, 3 months ago CC:
Aaron Boodman, abarth-chromium, chromium-reviews, darin (slow to review), qsr+mojo_chromium.org, viettrungluu+watch_chromium.org, yzshen+watch_chromium.org Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionUnbreak mac component build.
Components named "system" shadow /usr/lib/libSystem.dylib on OS X.
Give the component a different output name, and also add an action for
a while that cleans up libsystem.dylib from existing build dirs.
BUG=649696
Committed: https://crrev.com/0dfb6ba0b31eae8c8d2aab54ece37bb9ae29e9ea
Cr-Commit-Position: refs/heads/master@{#420752}
Patch Set 1 #
Messages
Total messages: 23 (11 generated)
The CQ bit was checked by thakis@chromium.org to run a CQ dry run
Dry run: CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
thakis@chromium.org changed reviewers: + rockot@chromium.org
LGTM, thanks
The CQ bit was unchecked by thakis@chromium.org
The CQ bit was checked by thakis@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
rsesek@chromium.org changed reviewers: + rsesek@chromium.org
Does rmdir_and_stamp.py not work (though I think the explicit args are better)? https://cs.chromium.org/chromium/src/build/rmdir_and_stamp.py?sq=package:chro...
On 2016/09/23 21:15:26, Robert Sesek wrote: > Does rmdir_and_stamp.py not work (though I think the explicit args are better)? > https://cs.chromium.org/chromium/src/build/rmdir_and_stamp.py?sq=package:chro... It probably does. I have a separate branch to remove that script since it looked unused. I guess I could use it here instead of deleting it and adding a very similar script...one sec.
The CQ bit was unchecked by thakis@chromium.org
On 2016/09/23 21:18:33, Nico wrote: > On 2016/09/23 21:15:26, Robert Sesek wrote: > > Does rmdir_and_stamp.py not work (though I think the explicit args are > better)? > > > https://cs.chromium.org/chromium/src/build/rmdir_and_stamp.py?sq=package:chro... > > It probably does. I have a separate branch to remove that script since it looked > unused. I guess I could use it here instead of deleting it and adding a very > similar script...one sec. Nope, doesn't work: FAILED: gen/mojo/public/cpp/system/clean_up_stamp python ../../build/rmdir_and_stamp.py libsystem.dylib gen/mojo/public/cpp/system/clean_up_stamp Traceback (most recent call last): File "../../build/rmdir_and_stamp.py", line 45, in <module> sys.exit(Main(sys.argv[1], sys.argv[2])) File "../../build/rmdir_and_stamp.py", line 40, in Main raise e OSError: [Errno 20] Not a directory: 'libsystem.dylib'
The CQ bit was checked by thakis@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
On 2016/09/23 21:20:28, Nico wrote: > On 2016/09/23 21:18:33, Nico wrote: > > On 2016/09/23 21:15:26, Robert Sesek wrote: > > > Does rmdir_and_stamp.py not work (though I think the explicit args are > > better)? > > > > > > https://cs.chromium.org/chromium/src/build/rmdir_and_stamp.py?sq=package:chro... > > > > It probably does. I have a separate branch to remove that script since it > looked > > unused. I guess I could use it here instead of deleting it and adding a very > > similar script...one sec. > > Nope, doesn't work: > > FAILED: gen/mojo/public/cpp/system/clean_up_stamp > python ../../build/rmdir_and_stamp.py libsystem.dylib > gen/mojo/public/cpp/system/clean_up_stamp > Traceback (most recent call last): > File "../../build/rmdir_and_stamp.py", line 45, in <module> > sys.exit(Main(sys.argv[1], sys.argv[2])) > File "../../build/rmdir_and_stamp.py", line 40, in Main > raise e > OSError: [Errno 20] Not a directory: 'libsystem.dylib' OK. It looks like rmdir_and_stamp.py is unused anyways, so you could just delete it instead :).
The CQ bit was unchecked by commit-bot@chromium.org
Try jobs failed on following builders: ios-device on master.tryserver.chromium.mac (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.mac/builders/ios-device/builds...)
The CQ bit was checked by thakis@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Description was changed from ========== Unbreak mac component build. Components named "system" shadow /usr/lib/libSystem.dylib on OS X. Give the component a different output name, and also add an action for a while that cleans up libsystem.dylib from existing build dirs. BUG=649696 ========== to ========== Unbreak mac component build. Components named "system" shadow /usr/lib/libSystem.dylib on OS X. Give the component a different output name, and also add an action for a while that cleans up libsystem.dylib from existing build dirs. BUG=649696 Committed: https://crrev.com/0dfb6ba0b31eae8c8d2aab54ece37bb9ae29e9ea Cr-Commit-Position: refs/heads/master@{#420752} ==========
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/0dfb6ba0b31eae8c8d2aab54ece37bb9ae29e9ea Cr-Commit-Position: refs/heads/master@{#420752} |