Remove the call to ccache to set run_second_cpp=true because ccache
no longer supports this option. See
https://ccache.dev/releasenotes.html#_ccache_4_12
for more information.
My reading of the ccache release notes & documentation is that when this
option was available the default was true. This is what we were setting
so removing it should not change behavior for ccache, at least most
recent versions. Commit
4cb5a590537a9caaf61db42ce8ea123d2ab961f3 seems
to be the source of this line that sets run_second_cpp=true but that
change does not clearly say why it is being explicitly set, so I think
it's safe to remove.
Signed-off-by: John Mulligan <jmulligan@redhat.com>
# remove the entropy generated by the date/time embedded in the build
$DRY_RUN export SOURCE_DATE_EPOCH="946684800"
$DRY_RUN ccache -o sloppiness=time_macros
- $DRY_RUN ccache -o run_second_cpp=true
if in_jenkins; then
# Build host has plenty of space available, let's use it to keep
# various versions of the built objects. This could increase the cache hit