WebRTC Native. cannot pass through "gclient sync" step

152 views
Skip to first unread message

Ilya Malyavskiy

unread,
Aug 3, 2018, 10:51:03 AM8/3/18
to discuss-webrtc
Hello Everyone. I'm new here and experiencing troubles with native libraries building.
I've fetched the master of the repository. Then executing "gclient sync" the output is the following:
=========================
Syncing projects:  36% (12/33) src/third_party                           
                                                                         
src/third_party (ERROR)                                                  
----------------------------------------                                 
[0:00:02] Started.                                                       
[0:00:29]    66bea27c42f..09ab2e00816  master     -> origin/master       
----------------------------------------                                 
Error: 6>                                                                
6> ____ src\third_party at a42c5d9439e306e6ade880a6e4aa9a21879c8c3b      
6>      You have unstaged changes.                                       
6>      Please commit, stash, or reset.                                  
=========================

This step passes well at 65th branch. But not on the master. 
May be I am doing something wrong?.. Any opinions?

Harald Alvestrand

unread,
Aug 3, 2018, 11:12:41 AM8/3/18
to WebRTC-discuss
6>      You have unstaged changes.                                       
6>      Please commit, stash, or reset.           

This is likely something left over in one of the repos that "gclient sync" tries to write to.
Dilligent use of "git status" (possibly iterating over the subdirectories) may uncover the culprit.


--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/2b0c7549-a027-43ca-a759-2a37797cafd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Ilya Malyavskiy

unread,
Aug 3, 2018, 11:18:47 AM8/3/18
to discuss-webrtc
Thank you for fast reply. I've just tested the 65th branch too and behavior is almost the same. Seems like you definitely right about things left after prev. sync. 
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.

Ilya Malyavskiy

unread,
Aug 3, 2018, 12:37:46 PM8/3/18
to discuss-webrtc
Got the reason of such kind failures: windows has a limitation for path length. If this limitation is exceeded the webrtc build system may report may not report... some strange errors can appear and so on.... so I would recommend to add some notice to do not put the webrtc-checkout folder to any place then a root dir of some local drive. And also take this point into account for the webrtc stuff updates to be aware that paths cannot exceed some maximum length.

witaly...@gmail.com

unread,
Nov 14, 2021, 11:38:04 PMNov 14
to discuss-webrtc
Just for posterity: the issue is still there, never been resolved (https://bugs.chromium.org/p/webrtc/issues/detail?id=8843), but there's a simple workaround which might worth mentioning in the WebRTC native API primer: adjust you Git config with "git config --system core.longpaths true", and all of a sudden it all works.
So at the end of the day it's a actually an issue with the default Git config on Windows.

Skilled fire

unread,
Dec 4, 2021, 2:46:44 PM (3 days ago) Dec 4
to discuss-webrtc

It's worth noting the 260 character path limit can be easily removed via registry "hacks" by following a guide like this. Maybe syncing should also modify the registry to remove the limitation, or at least prompt for it

Vitaly Ivanov

unread,
Dec 4, 2021, 9:10:55 PM (2 days ago) Dec 4
to discuss...@googlegroups.com
It doesn't help. I had long paths enabled in the registry, but it still failed

Michael Glenn Williams

unread,
Dec 4, 2021, 9:45:21 PM (2 days ago) Dec 4
to discuss...@googlegroups.com
So, for posterity what is Google's official O/S then ?

Reply all
Reply to author
Forward
0 new messages