On Jan 9, 5:00 pm, Robert Bradshaw <rober...@gmail.com> wrote:
> That defeats the purpose of sharing ccache across Sage builds.
That won't yield a benefit anyway. Quoting from the manpage:
"""
For both modes, the following information is included in the hash:
· the extension used by the compiler for a file with preprocessor
output (normally .i for C code and .ii for C++ code)
· the compiler\u2019s size and modification time (or other
compiler-specific information specified by CCACHE_COMPILERCHECK)
· the name of the compiler
· the current directory (if CCACHE_HASHDIR is set)
· contents of files specified by CCACHE_EXTRAFILES (if any)
"""
Note that the current directory, which is usually set in make, is
included. This is pretty much unavoidable: In direct mode, include
files are only considered by mtime. You could make identical c files
in different directories producing completely different results due to
the include files they refer to. In fact, due to the games that sage
plays with setting library inclusions and paths for finding all sorts
of files, it wouldn't surprise me if ccache's heuristics for reusing
information wouldn't be misled anyway across multiple sage installs.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To post to this group, send email to sage-devel@googlegroups.com.
To unsubscribe from this group, send email to
sage-devel+unsubscr...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
