Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Problem with build process #15320

Closed
misagogit opened this issue Feb 12, 2018 · 7 comments
Closed

Problem with build process #15320

misagogit opened this issue Feb 12, 2018 · 7 comments

Comments

@misagogit
Copy link

Hi. I'm trying to build the last stable version, 2.1.3 in a CentOs 7.4 but I receive an error message because the build.py file doesn't exist.

To do it,I have tried to build the tool following the build instructions (http://phantomjs.org/build.html):

$ git clone git://github.com/ariya/phantomjs.git
Cloning into 'phantomjs'...
remote: Counting objects: 65948, done.
remote: Compressing objects: 100% (52/52), done.
remote: Total 65948 (delta 28), reused 62 (delta 18), pack-reused 65871
Receiving objects: 100% (65948/65948), 161.23 MiB | 19.25 MiB/s, done.
Resolving deltas: 100% (28101/28101), done.
$ cd phantomjs
$ git checkout 2.1.3
Note: checking out '2.1.3'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b new_branch_name

HEAD is now at ca5a6c3... Fix #12090
$ git submodule init
$ git submodule update
$ python build.py
python: can't open file 'build.py': [Errno 2] No such file or directory

I'm using a normal user, not as a root user. Am I doing someting wrong? Thanks a lot.

@ghost
Copy link

ghost commented Feb 12, 2018

@misagogit please see #14585

@misagogit
Copy link
Author

Thanks for your reply, it seems that doing the checkout of the 2.1.0 version the build process works fine, but it could be good idea to have the buils instructions for the 2.1.3 updated in the website. Thanks.

@ghost
Copy link

ghost commented Feb 13, 2018

@misagogit The thing with website is that there is not much sense to update it, since I will update it once new version (2.1.4) is ready (public beta in mid-March). Once 2.1.4 reaches stability, 2.1.3 will enter first pre-EOL, and finally EOL phase (after 2 months of being in preEOL).

@vielmetti
Copy link

OK, so I understand that 2.1.1 is EOL and 2.1.3 does not build from source.

@ghost
Copy link

ghost commented Feb 16, 2018

@vielmetti yes: 2.1.1. is long EOL. 2.1.4 will (hopefully) build without making fuss....

@jan--f
Copy link

jan--f commented Mar 1, 2018

Any update on this? 2.1.1 is EOL as of today and there is no updated build instructions.

@ariya
Copy link
Owner

ariya commented Mar 3, 2018

Any plan beyond 2.1.1 is currently abandoned, see #15344 for more details.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants