Skip to content
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

Platform support for 'node' on PowerPC64LE #2205

Closed
sarveshtamba opened this issue Sep 26, 2019 · 6 comments
Closed

Platform support for 'node' on PowerPC64LE #2205

sarveshtamba opened this issue Sep 26, 2019 · 6 comments

Comments

@sarveshtamba
Copy link

  • I have been able to successfully deploy fabric8-launcher/launcher-operator on PowerPC64LE as mentioned in "Route Laucher not found on PPC64LE fabric8-launcher/launcher-operator#50 (comment)"

  • Currently working on step to "Install the Launcher (via the installed operator)". Facing issues with the example launcher yaml which makes use of image: fabric8/launcher-backend:latest, which for now is available only for x86_64.

  • I was facing the below failures on ppc64le while building fabric8/launcher-backend:

08:57:58.095 [main] INFO io.specto.hoverfly.junit.core.TempFileManager - Selecting the following binary based on the current operating system: hoverfly_linux_amd64

08:57:58.280 [Thread-2] INFO hoverfly - /root/fabric8/src/github.com/launcher-application/base/target/hoverfly.8425973283270400848/hoverfly_linux_amd64: /root/fabric8/src/github.com/launcher-application/base/target/hoverfly.8425973283270400848/hoverfly_linux_amd64: cannot execute binary file
  • Built hoverfly for ppc64le successfully using https://github.com/SpectoLabs/hoverfly and then tried to use this locally built hoverfly installation in the fabric8/launcher-backend build. However I was not successful in that, so by-passed the test cases which made use of hoverfly using the command mvn clean install -DskipTests:-

  • With this the build proceeded ahead, however it fails at the below step:-

[INFO] --- frontend-maven-plugin:1.8.0:install-node-and-yarn (install node and yarn) @ launcher-frontend ---
[INFO] Installing node version v11.12.0
[INFO] Unpacking /root/.m2/repository/com/github/eirslett/node/11.12.0/node-11.12.0-linux-ppc64le.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp
[INFO] Copying node binary from /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/tmp/node-v11.12.0-linux-ppc64le/bin/node to /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/node
[INFO] Installed node locally.
[INFO] Installing Yarn version v1.13.0
[INFO] Unpacking /root/.m2/repository/com/github/eirslett/yarn/1.13.0/yarn-1.13.0.tar.gz into /root/fabric8/src/github.com/launcher-application/frontend/target/frontend/node/yarn
[INFO] Installed Yarn locally.
[INFO]
[INFO] --- frontend-maven-plugin:1.8.0:yarn (yarn install) @ launcher-frontend ---
[INFO] Running 'yarn ' in /root/fabric8/src/github.com/launcher-application/frontend/target/frontend
[INFO] node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by node)
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for launcher-parent 1-SNAPSHOT:
[INFO]
[INFO] launcher-parent .................................... SUCCESS [  3.589 s]
[INFO] launcher-base-test ................................. SUCCESS [  3.395 s]
[INFO] launcher-base ...................................... SUCCESS [  7.860 s]
[INFO] launcher-creator ................................... SUCCESS [ 59.977 s]
[INFO] launcher-service-git-api ........................... SUCCESS [  1.927 s]
[INFO] launcher-service-openshift-api ..................... SUCCESS [  1.657 s]
[INFO] launcher-core-api .................................. SUCCESS [  3.983 s]
[INFO] launcher-service-git-impl .......................... SUCCESS [  5.672 s]
[INFO] launcher-service-openshift-impl .................... SUCCESS [  4.156 s]
[INFO] launcher-core-impl ................................. SUCCESS [  9.747 s]
[INFO] launcher-frontend .................................. FAILURE [  2.773 s]
[INFO] launcher-app ....................................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:47 min
[INFO] Finished at: 2019-09-25T08:24:12-04:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.8.0:yarn (yarn install) on project launcher-frontend: Failed to run task: 'yarn ' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <goals> -rf :launcher-frontend
  • I also built Node 11.12.0 locally on ppc64le successfully to workaround the above issue , but I was not able to make use of this in fabric8/launcher-backend build.
    Any way I can force the build system to use the node version that I have built locally?

  • Is node fully supported for PowerPC64LE and tested?

Any help towards this would be greatly appreciated.

@mhdawson
Copy link
Member

node is supported/tested on ppc64le, but there are minimum gblic levels for the community binaries.

Which OS and distro are you working on. My guess is that it might be RH 7.

We've been working to improve the level of support by moving the community builds from ubuntu to centos7 (which has an earlier glibc). The latest 12.x release should run on RH 7.
The next 10.x relesae should as well. There are no plans for 8.x

I think there will also be images from RH and/or versions of Node.js available through the RH software collections but we'd have to confirm they are available for PPC

@richardlau richardlau transferred this issue from nodejs/node Sep 26, 2019
@sam-github
Copy link

Have you tried installing libstdc++6 ? Its possible that's all you need to do to get node's official binaries to work.

@sarveshtamba
Copy link
Author

Hi @mhdawson @sam-github, using node v12.11.0 as below worked fine and I was able to complete the maven build:

diff --git a/frontend/pom.xml b/frontend/pom.xml
index f443c4e3..7d894672 100644
--- a/frontend/pom.xml
+++ b/frontend/pom.xml
@@ -30,7 +30,7 @@
               <goal>install-node-and-yarn</goal>
             </goals>
             <configuration>
-              <nodeVersion>v11.12.0</nodeVersion>
+              <nodeVersion>v12.11.0</nodeVersion>
               <yarnVersion>v1.13.0</yarnVersion>
             </configuration>
           </execution>

@mhdawson
Copy link
Member

@sarveshtamba great to hear :)

@mhdawson
Copy link
Member

@sarveshtamba any chance you could reach out to me through the email on my github id? I'd be interested in learning a bit about the work you are doing on the build scripts for PPCle

@sarveshtamba
Copy link
Author

@mhdawson check your mail.

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

No branches or pull requests

3 participants