ericmckean / naclports

Automatically exported from code.google.com/p/naclports
0 stars 0 forks source link

naclport for curl (i686, x86_64, arm) appears have been broken after March 25th updates #114

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download the naclports source files from Git into /tmp/naclports

   cd /tmp
   git clone https://chromimum.googlesource.com/external/naclports.git

2. Define NACL_SDK_ROOT to point to pepper_33 (also tried pepper_canary).

3. Define NACL_ARCH as i686 (x86_64 and arm also exhibit same issue).

4. Attempt to build the curl naclport.

   make curl

What is the expected output? What do you see instead?
Expected it to build and install the curl naclport for i686/x86_64/arm (like it 
does for pnacl).  Instead the build fails at line 672 of build_tools/common.sh 
with the following error:
  "/tmp/naclports/third_party/hterm/src/libdot/bin/concat.sh: No such file   or directory"
Note that a /tmp/naclports/third_party directory does not even exist.

What version of the product are you using? On what operating system?
Running on Ubuntu 12.10 with pepper_33.

Please provide any additional information below.
This worked fine before the massive updates made on March 25th.

Original issue reported on code.google.com by Nogginw...@gmail.com on 1 Apr 2014 at 10:00

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
Hopefully you figured this out.  Feel free to reopen if not.

Original comment by sbc@google.com on 19 Jun 2014 at 6:19