Closed denis-shienkov closed 5 years ago
The Python part is a red herring, the error is in node.js. My guess is that your version is too old.
My guess is that your version is too old.
A version of what? Python?
I have: python2 (v2.7.13) && python3 (v3.5.2)
My guess is that your version is too old.
A version of what? Python?
Of node.js.
Do note though that pyro as a branch is too old: it has GCC 6, which is too buggy and does not support enough C++14 to build Chromium successfully.
Of node.js.
Is it a host-side package, or it is a yocto-side package?
It's a Yocto package that runs on the host (i.e. we depend on nodejs-native
). On newer branches it's part of meta-openembedded.
Ok, many thanks..
But it is strange that chromium v63 does not compiled on 'pyro' branch, because from the 'meta-browser' commits log I see that it was checked on raspberry-pi && 'pyro' branch.
Ah, sorry, I didn't see you were building Chromium 63. I think that release still works with pyro and you can just find a newer nodejs recipe somewhere.
However, v63 is very old by Chromium's standards, and it is full of security issues. Please consider moving to the latest release we have here.
Ok, many thanks, I will try to upgrade my yocto at least to 'rocko', and then, step by step more.. :)
I just have updated the nodejs recipe to v8.4.0 (from 'rocko' branch) and then the chromium v63 compiled successfully. Many thanks.
Glad to hear that. Can we close this issue now?
Yes, please.
I have an yocto 'pyro' layer, where are I use the chromium v52. It was compiled fine... But then I have upgraded the chromium to v62 and more, then I got the compilation errors, related to the python:
`