In message: <20050619012425.L56734_at_fledge.watson.org> Robert Watson <rwatson_at_freebsd.org> writes: : : Observation on dependencies between components and nanobsd: : : In the old world order, dhclient backgrounded and waited for the link : state to come up. In the new world order, dhclient exits if the link : state is down, relying on devd to restart it. devd isn't build if NO_CXX : is set, as it's written in C++, and NO_CXX is a useful (and default) thing : to set for nanobsd for obvious reasons. It sounds like something here is : an argument for: : : - Allowing C++ to be built as a build dependency, but not installed. : - Rewriting devd to not be in C++. : - Providing an option so that dhclient's old and useful behavior can be : restored. It is generally desirable to have a separate 'install' environemnt from the 'build' environment on real embedded systems. The fact that nanobsd doesn't have this useful distinction is a problem with nanobsd, not devd. It should build everything, but install with all the NO_XXX flags set to do subsetting. devd won't be rewritten to not use C++. That's a non-option. WarnerReceived on Mon Jun 20 2005 - 16:48:39 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC