Date: Thu, 26 Aug 2004 00:01:44 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Maxim Sobolev <sobomax@portaone.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: ccache support for make buildworld/make release Message-ID: <20040825210144.GG35529@ip.net.ua> In-Reply-To: <412CFBED.6030508@portaone.com> References: <412CBC91.3070900@portaone.com> <412CD983.2040700@cronyx.ru> <20040825183342.GA81434@xor.obsecurity.org> <412CEF62.5010600@mcsi.pp.ru> <412CFBED.6030508@portaone.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Wtrm9ATX0sn6fFKv Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 25, 2004 at 11:51:57PM +0300, Maxim Sobolev wrote: > Yeah, I've noticed that as well. Also, for some reason when I've re-run= =20 > make world second time all objects built after buildtools miss the=20 > cache. Strange.... >=20 Does ccache take into account that the "cc" binary may be different for the same source and the command? What will happen, assuming it's made to work, if you attempt to build the native i386 world, and then try to "make buildworld TARGET_ARCH=3Dalpha"? The cc command will be the same; will ccache substitute the i386 code in this case? Also, what happens for a native build when we upgrade GCC version in the base? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --Wtrm9ATX0sn6fFKv Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (FreeBSD) iD8DBQFBLP44qRfpzJluFF4RAtXaAJ9HMPR5DlnxyRHC0zkoQ+SQQrnVQgCcCdvv 87SV41l6r4x7nRC2LasDHAM= =uX6d -----END PGP SIGNATURE----- --Wtrm9ATX0sn6fFKv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040825210144.GG35529>