Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
OpenBSD support, EPROTO question #71
Comments
@jirib defining it in src/include/pcp/config.h.in is the way to go - for example, see the EHOSTDOWN/ENODATA missing-error-code definitions there for Windows. From scanning the available error codes here: and looking at the places EPROTO is used, I'd suggest a better match (than EINTR) would be: | (Otherwise with diffs below I could build pcp on OpenBSD. Just build, I have to learn how to use it :) ) Good stuff! You might find the quick reference guide useful for getting a quick, practical introduction: |
|
Just a status update. The patches above are a start for an OpenBSD port, but they're not the whole story ... I have code base building now for OpenBSD and will post commits within a day or so. |
|
Latest commits resolve not only the EPROTO issue but a bunch of other porting issues that enable PCP to now build and run on OpenBSD ... so closing this issue. |
jirib commentedFeb 12, 2016
Hi,
I'm not really a developer so I'm asking before pull request? How to handle in better way EPROTO? It seems odd to have ifndef in couple of files?
(Otherwise with diffs below I could build pcp on OpenBSD. Just build, I have to learn how to use it :) )