I also saw that error happen with a hosed virtualenv (because of the hardcoded paths in the virtualenv scripts). In this case, just run `rm -rf python/_virtualenv` and restart your build.

        Fabrice

On 03/17/2017 09:40 AM, Emilio Cobos Álvarez wrote:
Seems like you don't have pip installed, have you followed all the steps
in the README to install the required dependencies?

 -- Emilio

On Fri, Mar 17, 2017 at 09:31:26AM -0700, ssriv...@ncsu.edu wrote:
I have pulled the latest code from servo github repository and I am using the 
following command to build the servo project on my Ubuntu machine:

    ./mach build --dev

but I get the following error:

    Traceback (most recent call last):
      File "./mach", line 92, in <module>
        main(sys.argv)
      File "./mach", line 23, in main
        mach = mach_bootstrap.bootstrap(topdir)
      File "/home/sumit/Documents/servo/python/mach_bootstrap.py", line 259, in 
bootstrap
        _activate_virtualenv(topdir, is_firefox)
      File "/home/sumit/Documents/servo/python/mach_bootstrap.py", line 194, in 
_activate_virtualenv
        process = Popen([pip, "install", "-q", "-I", "-r", req_path], 
stdout=PIPE, stderr=PIPE)
      File "/usr/lib/python2.7/subprocess.py", line 711, in __init__
    errread, errwrite)
      File "/usr/lib/python2.7/subprocess.py", line 1343, in _execute_child
    raise child_exception
    OSError: [Errno 2] No such file or directory


The build was happening successfully earlier on my machine, but it fails now. 
Could anyone please help me out?
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo


_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo


--
Fabrice Desré
Emerging Technologies
Mozilla Corporation
_______________________________________________
dev-servo mailing list
dev-servo@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-servo

Reply via email to