Bug 605732

Summary:	sys-devel/crossdev fails to compile glibc with default compiler set to clang
Product:	Gentoo Linux	Reporter:	Alexey <alexey+gentoo>
Component:	Current packages	Assignee:	Gentoo Toolchain Maintainers <toolchain>
Status:	CONFIRMED ---
Severity:	normal	CC:	chewi, embedded, kripton, telans
Priority:	Normal
Version:	unspecified
Hardware:	AMD64
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=723478
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	patch

Description Alexey 2017-01-15 01:01:44 UTC

I have CC="clang" CXX="clang++" in /etc/portage/make.conf
When trying to compile cross-armv7a-hardfloat-linux-gnueabi/glibc-2.23-r3:2.2, it tries to use clang instead of armv7a-hardfloat-linux-gnueabi-gcc, and fails with error "too old compiler".


Reproducible: Always

Steps to Reproduce:
1. Set clang as default compiler in make.conf
2. emerge cross-armv7a-hardfloat-linux-gnueabi/glibc
3.
Actual Results:  
clang is used, and ./configure fails

Expected Results:  
armv7a-hardfloat-linux-gnueabi-gcc should be used, because crossdev was initialialized with gcc, not with clang

Attaching the patch which I think should fix this. I managed to compile glibc only when I added this to /etc/portage/env/cross-armv7a-hardfloat-linux-gnueabi/glibc.conf

Comment 1 Alexey 2017-01-15 01:03:57 UTC

Created attachment 460084 [details, diff]
patch

Comment 2 James Beddek 2021-01-19 21:13:00 UTC

Thanks for the patch, fixes for me.

Comment 3 James Beddek 2021-11-30 01:53:08 UTC

(In reply to Alexey from comment #1)
> Created attachment 460084 [details, diff] [details, diff]
> patch

For crossdev to emerge mingw64-runtime correctly, `echo "CPP=''" >> "${output}"` must also be present for the __MINGW__ check in the mingw64-runtime ebuild

Comment 4 James Le Cuirot gentoo-dev

2025-01-04 08:27:39 UTC

This still doesn't work but for a different reason now. The glibc ebuild has code to force gcc. It is currently gated by an is_crosscompile condition. I think removing this should work, except that strip-unsupported-flags gets very confused and lets all the flags through, which usually breaks the build.