Hi, in the process of setting up a nanobsd-based system I've stumbled on so many issues during a make buildworld that I've started wondering whether NO_YP_LIBC is meant to work. Is anybody using it, and do you need local changes? Another question is what should it actually do. Parts of librpcsvc and libwrap call yp_*, as do libexec/{mknetid,ypxfr); it doesn't make sense to not compile YP support in libc but try (and fail) to compile these. Maybe we should have a single variable (NOYP or NO_YP, I don't care) that turns off all YP-only code. This is the way I'm pursuing locally; I've been slowly fixing issues as they come up (my buildworld machine is slow), I can post the resulting diffs as a starting point in case anybody cares. Bye, Andrea -- It's not a bug, it's tradition!Received on Tue Jun 22 2004 - 13:11:50 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:58 UTC