-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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
Compatibility with Solaris 10 #3408
Comments
@alexijs, We have used older Node.JS on Solaris 10 for some new features, but the main purpose of having Node.JS on Solaris 10 will be for a replacement Webserver. This Webserver hosts a wide-variety of non-Node.JS applications, many of which will not be migrated to Solaris 11 systems for a long time. Development of this Webserver is underway and operating on Solaris 11 at this time. The other 'new features' are running on Peter Tribble's builds. The features are not directly accessible so security (keeping node up-to-date) is less of a concern. Actually, some of these features were introduced on Node 0.4.7 which I built on Solaris 11 Express, and then transferred the binaries to Solaris 10. (yes, it used to be possible this way) I know that today these will have to be built on Solaris 10 for Solaris 10, so I'll be setting up a build environment soon and post results in a new issue. |
It is possible these legacy systems will be upgraded to sooner than I thought. I'm closing this issue for now. |
With Solaris 11 errors resolved, I'm going to try to build on Solaris 10 soon and post some specific details of any compatibility problems. For now this is a placeholder for conversations related to Solaris 10.
The text was updated successfully, but these errors were encountered: