On Tue, Jan 15, 2013 at 03:35:25PM -0800, Steve Kargl wrote: > It seems that buildworld depends on the existence of > /usr/bin/compile_et if one wants to build WITH_KERBEROS > on a system that has never had Kerberos support. I > discovered this issue when des_at_ removed the NOFOO and > NO_FOO options, and the NO_KERBEROS="YES" in my > /etc/make.conf was neutered. The system in question > has never had kerneros installed. One can emulate > the problem as follows: > For what it is worth, reverting the removal of NO_FOO, et. al, will not fix your issue. I ran into this several months ago, and found out "the hard way" that many of our ports require kerberos, even if they do not advertise it - so building without kerberos on the system would fail. I started digging into it, and found what you found - compile_et does not get built prior to building the kerberos bits. It actually gets quite worse from there. I do not recall the details off-hand, but I recall doing 'make obj all install' in somewhat this order: - secure/ - include/ - kerberos5/ [some steps may be missing] Once I had compile_et, install_et, and a few things I do not recall right now, I could then go through and do a full buildworld/installworld. I never got much further in tracking this down. :( Glen
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:34 UTC