Issue metadata
Sign in to add a comment
|
gclient sync fails for Android on a case-insensitive filesystem
Reported by
antonis....@telestax.com,
Feb 28 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Steps to reproduce the problem: 1. Follow steps at https://webrtc.org/native-code/android/ until 'gclient sync' command that fails What is the expected behavior? That sync will be successful What went wrong? $ gclient sync ________ running '/usr/bin/python src/cleanup_links.py' in '/vagrant/webrtc-checkout' Syncing projects: 100% (43/43) src/third_party/android_tools/ndk src/third_party/android_tools/ndk (ERROR) ---------------------------------------- [0:02:16] Started. ---------------------------------------- Error: 43> Did this work before? Yes I believe webrtc #13886 was working fine, now I'm building #16726 Chrome version: 56.0.2924.87 Channel: stable OS Version: OS X 10.11.6 Flash Version: - First off I first reported this to webrtc project (https://bugs.chromium.org/p/webrtc/issues/detail?id=7197), but was told that I should report here instead. - As a build machine I'm using an Ubuntu Linux VM running inside Mac OSX 10.11.6 - The exact same virtual machine used to work a couple of months back, not sure what changed. - I have traced the issue down to the case insensitivity of default Mac filesystem that hosts the webrtc repository locally which combined with some idiosyncracies of src/third_party/android_tools/ndk/* files doesn't allow git to manage files properly. - Notice that I managed to workaround the issue by creating a separate partition, one which is case sensitive and host the repo there. But the question is can you fix it so webrtc can be build in Linux when ran in a virtual machine inside Mac OS. Seems to me a pretty common use case
,
Mar 1 2017
This looks like out of scope for TE, hence adding the respective label for it to triage further.
,
Mar 1 2017
,
Mar 5 2017
If the issue is in src/third_party/android_tools/ndk/*, the report may need to go to https://source.android.com/source/report-bugs.html
,
Mar 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 12 2018
I suspect this got fixed. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by pfeldman@chromium.org
, Feb 28 2017