You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug #112449 hides clang arguments in a "response file" by default if isClang is true, but ccache does not support this and responds with "no input files" instead.
Additional context
The following workaround can be used to disable response files in a ccacheWrapper result cc, fixing the issue:
# a list of nixpkgs attributes affected by the problemattribute: ccacheWrapper ccacheStdenv# a list of nixos modules affected by the problemmodule: programs.ccache
The text was updated successfully, but these errors were encountered:
Can we perhaps add a export NIX_CC_USE_RESPONSE_FILE=0 to the ccache-links wrapper (gated on isClang, maybe)?
Edit: my bad, that doesn't work; we need the env var to be set before the outer layer of stdenv wrapper machinery runs. By the time we're in the ccache wrapper it's too late.
It's also not clear to me if this is a bug in ccache or intended behavior (I was not able to find an issue for it upstream) but it's definitely reproducible:
Describe the bug
#112449 hides clang arguments in a "response file" by default if
isClang
is true, but ccache does not support this and responds with "no input files" instead.Additional context
The following workaround can be used to disable response files in a
ccacheWrapper
resultcc
, fixing the issue:Notify maintainers
@angerman
Maintainer information:
The text was updated successfully, but these errors were encountered: