[LLVMbugs] [Bug 13282] New: ccache, distcc and others interfere with clang execution

[bugzilla-daemon at llvm.org]

http://llvm.org/bugs/show_bug.cgi?id=13282

             Bug #: 13282
           Summary: ccache, distcc and others interfere with clang
                    execution
           Product: clang
           Version: 3.1
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: -New Bugs
        AssignedTo: unassignedclangbugs at nondot.org
        ReportedBy: c.kworr at gmail.com
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified


This is just a wild guess though, but long time ago I found that using ccache
with clang is really-really painful:

https://bugzilla.samba.org/show_bug.cgi?id=8460

It seems that when enabling ccache clang command line becomes severely
distorted. For nothing.

I think that the difference is in how GCC works. Or exactly what GCC executes.
cpp never call cpp again, it calls cc1plus. Whereas clang calls clang again,
and if we don't specify full path to called binary ccache jumps in, parses
flags and reexecutes clang. This step may be undesirable. Would it be better to
record location of clang and when calling clang again use full path to prohibit
stealing this call?

-- 
Configure bugmail: http://llvm.org/bugs/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.