-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V8 compilation error on PPC #119
Comments
It seems like |
where should I add the flag? |
Flag should be added to the Jenkins job which runs
|
It builds, but hits another error:
|
I checked out I did however get the above error on a V8 checkout with older dependencies, running "gclient sync" fixed it. Could you try rerunning a fresh Jenkins job? I also don't have access to that machine, could you please add my key for any further investigations, I got permission here: nodejs/build#1706
|
/cc @nodejs/build-infra ^ |
Anyone with @nodejs/build access can add authorized keys to test machines (if an issue exists to say its OK!). I added @miladfarca. |
There seems to be a bug in Python versions prior to Python version on this machine is This is the V8 CL which has introduced this issue: I have asked the owner for a possible workaround (or python has to be upgraded/patched). |
I can schedule python updates if it ends up that is what's necessary. It'll require updates to all the ansilbe scripts that build python for those hosts (likely, unless some are getting it from package repos with updates, but thats not likely). I'd need an explicit list of hosts that need the update - all Also, I'd need a minimum python2 version. |
Thanks Sam, Let's see if it gets accepted considering Python 3 is going to replace it sometime very soon. If not then we might have to upgrade Python to at-least |
above CL is now landed. Issue should be solved on the next lkgr build. |
Thanks. Before closing this, can I ask why |
We always had this flag in our V8 internal builds, I feel this might be a gcc limitation where not having the backtrace symbols causes lambda related syntax errors. More info can be found here: |
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: #32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
Refs: nodejs/node-v8#119 PR-URL: nodejs#32113 Reviewed-By: Ben Noordhuis <[email protected]> Reviewed-By: Michael Dawson <[email protected]> Reviewed-By: Anna Henningsen <[email protected]>
See: https://ci.nodejs.org/job/node-test-commit-v8-linux/2590/nodes=ppcle-ubuntu1404,v8test=v8test/console
@nodejs/platform-ppc
The text was updated successfully, but these errors were encountered: