Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 821580

Summary: sys-cluster/ceph-16.2.6-r2 fails to compile
Product: Gentoo Linux Reporter: Agostino Sarubbo <ago>
Component: Current packagesAssignee: Patrick McLean <chutzpah>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cluster, dlan
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build.log.xz
1-project-config.jam
2-project-config.jam
3-project-config.jam

Description Agostino Sarubbo gentoo-dev 2021-11-04 06:00:18 UTC
https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sys-cluster/ceph-16.2.6-r2 fails to compile.
Discovered on: amd64 (internal ref: ci)

NOTE:
This machine uses GCC-11: https://gcc.gnu.org/gcc-11/porting_to.html
If you think this is a GCC-11 related issue, please block bug 732706.
Comment 1 Agostino Sarubbo gentoo-dev 2021-11-04 06:00:21 UTC
Created attachment 748380 [details]
build.log.xz

build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)
Comment 2 Agostino Sarubbo gentoo-dev 2021-11-04 06:00:22 UTC
Created attachment 748383 [details]
1-project-config.jam

1-project-config.jam
Comment 3 Agostino Sarubbo gentoo-dev 2021-11-04 06:00:23 UTC
Created attachment 748386 [details]
2-project-config.jam

2-project-config.jam
Comment 4 Agostino Sarubbo gentoo-dev 2021-11-04 06:00:24 UTC
Created attachment 748389 [details]
3-project-config.jam

3-project-config.jam
Comment 5 Agostino Sarubbo gentoo-dev 2021-11-04 06:00:25 UTC
Possible context of error(s):

-- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) 
x86_64-pc-linux-gnu-gcc: error: 0: linker input file not found: No such file or directory
x86_64-pc-linux-gnu-gcc: error: ##: linker input file not found: No such file or directory
x86_64-pc-linux-gnu-gcc: error: ##: linker input file not found: No such file or directory
Comment 6 Patrick McLean gentoo-dev 2021-11-08 19:02:13 UTC

*** This bug has been marked as a duplicate of bug 802150 ***