0Environment variables and search paths can drastically effect the
1operation of build tools.
2
3Include these in our id string to mitigate against false cache hits.
Note to builders: This will invalidate all depends output caches in BASE_CACHE
0Environment variables and search paths can drastically effect the
1operation of build tools.
2
3Include these in our id string to mitigate against false cache hits.
Note to builders: This will invalidate all depends output caches in BASE_CACHE
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
No conflicts as of last run.
gcc -v -E -
seems to lose COLLECT_LTO_WRAPPER
…
Concept ACK. If I understand it correctly, this includes only specific targeted environment variables and not the entire env?
Yes! It automatically includes any env var that starts with the name of the tool (e.g. STRIP_*
for strip
), and if there are particular ones we know about (e.g. ZERO_AR_DATE
) we can just append it like so: 6ee5ee4
(#20629)
gcc -v -E -
seems to loseCOLLECT_LTO_WRAPPER
…
Right, perhaps someone knows a better invocation here? I’m guessing COLLECT_LTO_WRAPPER
is omitted because the linker is not going to run?
Pushed 4b9aaca598aea561d44215eecd3c4a01d08ddd5a -> f792069bc117f11dff0db11f9386ec216581d2a2
Previously, if the value contained syntax that was meaningful to make,
the printing would fail. Quoting properly avoids this.
Environment variables and search paths can drastically effect the
operation of build tools.
Include these in our id string to mitigate against false cache hits.
dongcarl
DrahtBot
laanwj
luke-jr
Labels
Build system