Bug 1996936

Summary: ccache: FTBFS in Fedora 34
Product: [Fedora] Fedora Reporter: Orion Poplawski <orion>
Component: ccacheAssignee: Michael Cullen <michael>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 34CC: adev88, michael, orion
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://koschei.fedoraproject.org/package/ccache
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-07 23:57:06 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2043970    
Attachments:
Description Flags
4.4.2 patch none

Description Orion Poplawski 2021-08-24 04:02:26 UTC 
Description of problem:
Package ccache fails to build from source in Fedora 34.

Version-Release number of selected component (if applicable):
4.2-1.fc34

Steps to Reproduce:
koji build --scratch f34 ccache-4.2-1.fc34.src.rpm

Additional info:
This package is tracked by Koschei. See:
https://koschei.fedoraproject.org/package/ccache

Test failure on some arches:
 2/36 Test  #8: test.debug_prefix_map ............***Failed    0.64 sec
Compiler:         gcc (/usr/bin/gcc)
Compiler version: gcc (GCC) 11.2.1 20210728 (Red Hat 11.2.1-1)
CUDA compiler:    not available
Running test suite debug_prefix_map.
FAILED
Test suite:     debug_prefix_map (line 33)
Test case:      Mapping of debug info CWD
Failure reason: File test.o contains "/builddir/build/BUILD/ccache-4.2.1/redhat-linux-build/testdir/430408/run/dir1"
ccache -s:
cache directory                     /builddir/build/BUILD/ccache-4.2.1/redhat-linux-build/testdir/430408/.ccache
primary config                      /builddir/build/BUILD/ccache-4.2.1/redhat-linux-build/testdir/430408/.ccache/ccache.conf
secondary config (readonly)         
stats updated                       Sun Aug 22 06:57:10 2021
cache hit (direct)                     0
cache hit (preprocessed)               0
cache miss                             1
cache hit rate                      0.00 %
cleanups performed                     0
files in cache                         2
cache size                           8.2 kB
max cache size                       5.0 GB

I tried updating to 4.4 but the failure persists so I reported it upstream.
Comment 1 Xose Vazquez Perez 2021-10-13 21:00:12 UTC 
Created attachment 1832711 [details]
4.4.2 patch

fixes to build 4.4.2
Comment 2 Xose Vazquez Perez 2021-11-18 14:07:26 UTC 
It was done, and this bug should be closed:
https://koji.fedoraproject.org/koji/packageinfo?packageID=1442

Thanks.
Comment 3 Ben Cotton 2022-05-12 16:13:44 UTC 
This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.
Comment 4 Ben Cotton 2022-06-07 23:57:06 UTC 
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.