I was always wondering why sci-chemistry/gromacs takes so long to recompile, but it uses cc (not gcc) as compiler, which is not cached by ccache. Why is that? Btw: It should be posible to cache icc as well.
Using commit message: ------------------------------------------------------------------------------ Fix bug #302048. thanks to Christoph Junghans (Portage version: 2.2_rc61/cvs/Linux x86_64) ------------------------------------------------------------------------------ /var/cvsroot/gentoo-x86/sci-chemistry/gromacs/files/gromacs-4.0.9999-docdir.patch,v <-- files/gromacs-4.0.9999-docdir.patch initial revision: 1.1 /var/cvsroot/gentoo-x86/sci-chemistry/gromacs/files/gromacs-4.0.9999-configure-gfortran.patch,v <-- files/gromacs-4.0.9999-configure-gfortran.patch initial revision: 1.1 /var/cvsroot/gentoo-x86/sci-chemistry/gromacs/files/gromacs-4.0.9999-ccache.patch,v <-- files/gromacs-4.0.9999-ccache.patch initial revision: 1.1 /var/cvsroot/gentoo-x86/sci-chemistry/gromacs/ChangeLog,v <-- ChangeLog new revision: 1.49; previous revision: 1.48 /var/cvsroot/gentoo-x86/sci-chemistry/gromacs/gromacs-4.0.7-r1.ebuild,v <-- gromacs-4.0.7-r1.ebuild initial revision: 1.1
Thanks for committing the fix for gromacs to the tree. But this a bug in ccache -> Reopen It should have a link /usr/lib/ccache/bin/cc -> /usr/bin/cc
(In reply to comment #2) > Thanks for committing the fix for gromacs to the tree. > > But this a bug in ccache -> Reopen > > It should have a link > /usr/lib/ccache/bin/cc -> /usr/bin/cc > No, you should set the CC env var and the build system should use that instead of guessing what cc to use.
I see, even if I don't like the solution. Btw, why does `ccache-config --install-links` creates a link for cc then?
(In reply to comment #4) > I see, even if I don't like the solution. > > Btw, why does `ccache-config --install-links` creates a link for cc then? > Agree. It should create such links
I fixed the problem in the gromacs ebuild, but I still think cc should be cached.
looks like the ebuild and ccache-config are out of sync. the ebuild does not make a "cc" symlink, and it explicitly deletes "cc" and "CHOST-cc". the ccache-config script however creates both "cc" and "CHOST-cc". so i cleaned up the ccache-config script to respect $ROOT and to not create a "CHOST-cc", then i punted all the logic from the ebuild in favor of it just running the ccache-config script. i dont think these symlinks belong in the pkg manifest anyways. http://sources.gentoo.org/dev-util/ccache/files/ccache-config?r1=1.2&r2=1.3