Github user mateiz commented on the pull request:

    https://github.com/apache/spark/pull/258#issuecomment-38843162
  
    @nicklan I actually see some other errors due to pushd and popd now:
    ```
    ./make-distribution.sh: line 133: pushd: no other directory
    Fetchting tachyon tgz
    --2014-03-27 11:31:11--  
https://github.com/amplab/tachyon/releases/download/v0.4.1/tachyon-0.4.1-bin.tar.gz
    Resolving github.com... 192.30.252.131
    Connecting to github.com|192.30.252.131|:443... connected.
    HTTP request sent, awaiting response... 302 Found
    Location: 
https://s3.amazonaws.com/github-cloud/releases/7276954/dedb4c68-a574-11e3-960d-341edab9bc3c.gz?response-content-disposition=attachment%3B%20filename%3Dtachyon-0.4.1-bin.tar.gz&AWSAccessKeyId=AKIAISTNZFOVBIJMK3TQ&Expires=1395945132&Signature=3%2FZTB8tWWf89B8pc2duZ6gl6n%2F4%3D
 [following]
    --2014-03-27 11:31:12--  
https://s3.amazonaws.com/github-cloud/releases/7276954/dedb4c68-a574-11e3-960d-341edab9bc3c.gz?response-content-disposition=attachment%3B%20filename%3Dtachyon-0.4.1-bin.tar.gz&AWSAccessKeyId=AKIAISTNZFOVBIJMK3TQ&Expires=1395945132&Signature=3%2FZTB8tWWf89B8pc2duZ6gl6n%2F4%3D
    Resolving s3.amazonaws.com... 207.171.189.80
    Connecting to s3.amazonaws.com|207.171.189.80|:443... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 22751619 (22M) [application/octet-stream]
    Saving to: 'tachyon-0.4.1-bin.tar.gz'
    
    100%[======================================>] 22,751,619  3.79MB/s   in 
9.5s   
    
    2014-03-27 11:31:23 (2.28 MB/s) - 'tachyon-0.4.1-bin.tar.gz' saved 
[22751619/22751619]
    
    ./make-distribution.sh: line 151: popd: directory stack empty
    ```
    
    Haven't looked into it much, see if you can get someone with a Mac to work 
with.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to