-
Notifications
You must be signed in to change notification settings - Fork 19
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
SmartOS / Solaris #12
Comments
Definitely willing to help out here! However since the implications of this are a bit bigger then just fixing the bcrypt package build which I did previously I would like to ping @jperkin. He is probably way more impacted then me on anything that is decided here. It might also be an idea to make a shift between Illumos and Solaris while we are at it since those are slowly drifting apart. |
@siepkes if this is intended for pkgsrc then we would likely completely ignore this kind of section, it's way too OS-specific, so I wouldn't worry too much about it. |
I am also a bit surprised by the specificity of this section from the erlang makefiles. Would be good to at least have it build and work on Solaris/SmartOS and/or illumos. As I don't have access to these OS's I would be grateful if you could add the correct options and make it work on one or more of those OS's. I also suspect that the "Linux" section could be the more generic fallback. When we have fixed this, then I will include it into the 1.2.0 |
@mworrell In which repo is the Makefile you reference so I can add the flags, test it and make a PR for it? |
hi @siepkes, the Makefile is here: https://github.com/erlangpack/bcrypt/blob/master/c_src/Makefile This is a new Makefile (derived from erlang-mk) as we are now using rebar3. And also Windows... we might want to change the Linux entry into a catch-all. |
I changed the FreeBSD entry into a catch all. |
@Licenser and @siepkes we have released 1.1.0 - but I now realize that our new
Makefile
(based on erlang-mk) does not include any special options for Solaris or SmartOS.Could you have a look?
The text was updated successfully, but these errors were encountered: