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

Wrong architecture selected on 64 bit OS with 32 bit Java #8

Open
neykov opened this issue Jul 21, 2014 · 2 comments
Open

Wrong architecture selected on 64 bit OS with 32 bit Java #8

neykov opened this issue Jul 21, 2014 · 2 comments
Assignees

Comments

@neykov
Copy link

neykov commented Jul 21, 2014

On 64 bit Linux with 32 bit Java "os.arch" is reported as "i386" which leads to the wrong nodejs executable extracted. The plugin extracts the 32 bit binary on 64 bit OS which leads to the error "_libstdc++.so.6: cannot open shared object file_" when trying to execute the server.

On Windows the wrong executable is used as well but the OS handles it transparently.

@skwakman
Copy link
Owner

sorry for the delayed response. I'll see if I can find a solution for this issue in the next few days. Perhaps offering an option override for situations where os.arch is not enough?

@neykov
Copy link
Author

neykov commented Aug 20, 2014

Just saw your questions, override wouldn't help because the same pom is used in multiple environments, setting a static override will be worse. When researching the problem the only reliable approach to get the architecture seemed to be executing native commands, like "uname -p". If that fails you could fall back to the java properties.

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

2 participants