Closed GoogleCodeExporter closed 9 years ago
The problem I think is that third_party stuff is pulled in by gclient (see the
DEPS file).
While you can build most ports with a basic git checkout, anything that uses
hterm needs be checked out with gclient.
I don't think this is related to recent changes.
Original comment by sbc@chromium.org
on 1 Apr 2014 at 10:12
So I installed depot_tools using the following:
git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
And then I set my PATH with the following command:
export PATH=$PATH:`pwd`/depot_tools
Then I reran the "make curl" and got the same error.
What am I missing here? So hterm gets pulled into the third_party directory by
some the naclports scripts (via gclient)? If so, does gclient require any
special TCP ports be opened on our firewall. I'm behind a corporate firewall
and its locked down pretty tight.
Original comment by Nogginw...@gmail.com
on 1 Apr 2014 at 11:04
You need to use gclient to do the checkout. The instructions are here:
https://code.google.com/p/naclports/wiki/HowTo_Checkout
Specifically 'glclient sync' is the command the updates the things in
third_party.
Original comment by sbc@google.com
on 1 Apr 2014 at 11:35
I'm kind of at a loss as to what I need to do to get this to install properly.
I've got subversion and gsutil installed, but the scripts just won't install
curl.
What's interesting is libcurl.a (which is what I need) does get built in the
out/build/curl directory, but the install bombs out. As a result, the headers
and lib don't get copied to the toolchain directories. I'm tempted to copy
them manually until this problem can be resolved.
I'm not sure why this doesn't happen with pnacl too.
Original comment by Nogginw...@gmail.com
on 1 Apr 2014 at 11:42
Ok, I will try what you described later this evening.
https://code.google.com/p/naclports/wiki/HowTo_Checkout
Thanks for your help.
Original comment by Nogginw...@gmail.com
on 1 Apr 2014 at 11:44
Hopefully you figured this out. Feel free to reopen if not.
Original comment by sbc@google.com
on 19 Jun 2014 at 6:19
Original issue reported on code.google.com by
Nogginw...@gmail.com
on 1 Apr 2014 at 10:00