Date: Thu, 24 Dec 2009 10:06:31 -0700 (MST) From: "M. Warner Losh" <imp@bsdimp.com> To: ru@freebsd.org Cc: dougb@freebsd.org, jhb@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org, marius@alchemy.franken.de, svn-src-head@freebsd.org Subject: Re: svn commit: r200797 - head/lib/libc/stdtime Message-ID: <20091224.100631.354966604298475976.imp@bsdimp.com> In-Reply-To: <20091224144136.GA28793@edoofus.dev.vega.ru> References: <20091221.211648.632868945383134253.imp@bsdimp.com> <4B3129CD.20908@FreeBSD.org> <20091224144136.GA28793@edoofus.dev.vega.ru>
index | next in thread | previous in thread | raw e-mail
In message: <20091224144136.GA28793@edoofus.dev.vega.ru>
Ruslan Ermilov <ru@freebsd.org> writes:
: On Tue, Dec 22, 2009 at 12:19:25PM -0800, Doug Barton wrote:
: > In the short term I think we are well served on all fronts to modify
: > the build architecture to better support compilers from ports. This
: > would actually help with the llvm/clang testing too, and sidestep the
: > problems of gplv3 stuff being in the base. TMK there has been no work
: > on this direction at all, which is disappointing.
:
: If you take GNU binutils/compiler from ports, I think we can already
: do this, and without any changes to the build architecture. It's
: just a matter of defining several make(1) variables, like CC, CXX,
: CPP, LD, AS, NM, AR, specifying full paths of the desired binaries,
: plus some environment variables (at least STRIPBIN, so that install(1)
: calls the correct strip(1) binary).
Don't you have to replace them as a pair? And the list of variables
is kinda long... And there's no real way to say use gcc from the
tree, but use binutils from ports.
Warner
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091224.100631.354966604298475976.imp>