Bug 885773

Summary:	[fem-overlay] dev-perl/Net-Libdnet-0.99-r1 calls cc directly
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Overlays	Assignee:	Paul Michel <frainz>
Status:	RESOLVED FIXED
Severity:	normal	CC:	fem-overlay, nex+b-g-o
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://gitlab.fem-net.de/gentoo/fem-overlay/-/issues/186
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	build.log

Description Agostino Sarubbo gentoo-dev

2022-12-13 11:35:42 UTC

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: dev-perl/Net-Libdnet-0.99-r1 calls cc directly.
Discovered on: amd64 (internal ref: fem-overlay_tinderbox)

NOTE:
As per QA policy, toolchain tools must not be called directly because they can cause issue in cross-compiling and because is not possible use a different CC implementation (like clang). To reproduce, please use sys-devel/gcc-config[-native-symlinks], sys-devel/binutils-config[-native-symlinks].

Comment 1 Agostino Sarubbo gentoo-dev

2022-12-13 11:35:44 UTC

Created attachment 842453 [details]
build.log

build log and emerge --info

Comment 2 Agostino Sarubbo gentoo-dev

2022-12-13 11:35:45 UTC

Error(s) that match a know pattern:

cc1: error: ‘-Werror=incompatible-function-pointer-types’: no option ‘-Wincompatible-function-pointer-types’; did you mean ‘-Wincompatible-pointer-types’?

Comment 3 Adrian Schollmeyer 2022-12-27 15:38:13 UTC

Is this really an issue with

Comment 4 Adrian Schollmeyer 2022-12-27 15:39:22 UTC

Is this really an issue with cc being called directly or rather an unsupported compiler option being passed? build.log indicates that cc isn't called directly, but x86_64-pc-linux-gnu-gcc.

Comment 5 Paul Michel 2023-07-09 21:03:23 UTC

Issue closed upstream, see GitLab issue #186