Date: Mon, 20 Jun 2005 12:49:05 -0600 (MDT) From: "M. Warner Losh" <imp@bsdimp.com> To: rwatson@freebsd.org Cc: current@freebsd.org Subject: Re: dhclient less functional with nanobsd because of NO_CXX Message-ID: <20050620.124905.35871665.imp@bsdimp.com> In-Reply-To: <20050619012425.L56734@fledge.watson.org> References: <20050619012425.L56734@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message: <20050619012425.L56734@fledge.watson.org>
Robert Watson <rwatson@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.
Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050620.124905.35871665.imp>