Le vendredi 30 avril 2010 à 00:16 +0200, Rémi Cardona a écrit : > Le 29/04/2010 09:06, "Paweł Hajdan, Jr." a écrit : > > What actions would you suggest? > > Don't use ccache. We (speaking as a former gnome herd member) have had > countless unexplained bugs due to ccache. > > Now, the gnome procedure for build failures is to ask users to first > disable distcc and ccache before trying to reproduce the bug, and that > solves nearly all the weird issues that no-one else can reproduce. > > Bottom line, unless you're building the same code over and over again, > don't use ccache. And even if you are, don't use it, its cache is just > too easily broken. > > Cheers,
Not that countless. Personal experience reports one bug in 8 years of use... Just as was previously mentioned in this thread: * check your hardware * know your FEATURES and howto test failures when some are enabled it's just like any package failing with some gcc/linked/whatever flag, you just don't stop using that flag where it works just because of one package, nor do you stop using gcc. -- Gilles Dartiguelongue <e...@gentoo.org> Gentoo
signature.asc
Description: Ceci est une partie de message numériquement signée
