-
Notifications
You must be signed in to change notification settings - Fork 49
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
libnsl dependency #254
Comments
I haven't tried running it, but it builds fine if you comment out the nsl bits in CMakeLists.txt |
So do you think the requirement is obsolete? |
I take it back, it built because I have libnsl installed. libnsl provides NIS/YP, and this is used in ntirpc in several places, so it is, indeed, necessary. |
Is there any way we can make libnsl optional for installations that don't use NIS/YP? |
I removed the libnsl detection from CMakesLists and i was able to build. I cross compiled as an easy way to make sure my machine did not contaminate the build. I searched for inclusion of headers from libnsl and
But from my compilation log some of these files are not compiled and the ones that are already have a #ifdef YP. So i guess we can just add the #ifdef YP to the remaining files just in case they are built in a configuration i maybe missing. |
Patch submitted in pull request #255 |
NIS(Network Information Service), which manages accounts for other Linux hosts. Originally, it was known as Sun Yellow Pages (abbreviated as yp). Nowadays, it has largely been replaced by LDAP and is not of much use anymore. So, I'm wondering if there are still some scenarios where the NIS service is needed. |
The patch was submitted over two years ago and has not been merged. Is this still an issue? Can we close it? |
Hello
I am trying to build ntirpc without libnsl2 in linux (non BSD). The reason I would like it to be possible is because libnsl2 in turn depends on a RPC implementation thus creating a circular dependency. Do you know if it is possible to build ntirpc without libnsl2?
The text was updated successfully, but these errors were encountered: