Closed GoogleCodeExporter closed 9 years ago
Sounds similar to https://code.google.com/p/libyuv/issues/detail?id=329
depot tools (gclient sync) are supported by chromium and also used for webrtc.
What distro of linux are you on?
Original comment by fbarch...@chromium.org
on 11 Jun 2014 at 9:13
my apologies for the incomplete post.
What steps will reproduce the problem?
1. svn the depot_tools
2. set absolute path till libyuc
3. ./gclient sync
What version of the product are you using? On what operating system?
i followed the WebRtc2SIP technical guide. using CentOS 6.5 32 bit
Original comment by habibsha...@gmail.com
on 12 Jun 2014 at 3:53
This seems like a duplicate of bug 329
https://code.google.com/p/libyuv/issues/detail?id=329
which concluded there is a work around or fix, but not what it is.
gclient sync is supported by chromium team, so its likely any fix or bug report
will need to be with them.
Original comment by fbarch...@chromium.org
on 27 Jun 2014 at 12:59
DETECT_HOST_ARCH comes from the chromium scripts which dont explicitly support
CentOS.
If a fix is needed it'll need to be in the chromium code or depot tools.
Best bet would be search for work arounds that chromium or webrtc developers
may have found.
kjellander may have more knowledge on the topic, but is away at the moment.
As a work around, other build systems could be used, including make.
Original comment by fbarch...@chromium.org
on 15 Jul 2014 at 12:19
I don't know much about this problem, but what about trying to set the
environment variable GYP_DEFINES like this and re-run the sync?
export GYP_DEFINES="host_arch=ia32"
gclient sync
Looking at
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/binutils/
download.py&l=43
it seems that might work as a workaround.
Original comment by kjellan...@google.com
on 15 Jul 2014 at 3:03
Updated Getting started wiki with that work around.
Much of the code is now synced thru chromium and git. So everything will
change... hopefully for the better.
Original comment by fbarch...@google.com
on 17 Dec 2014 at 12:16
Original issue reported on code.google.com by
habibsha...@gmail.com
on 11 Jun 2014 at 6:54