Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 605732 - sys-devel/crossdev fails to compile glibc with default compiler set to clang
Summary: sys-devel/crossdev fails to compile glibc with default compiler set to clang
Status: CONFIRMED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal
Assignee: Gentoo Toolchain Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-15 01:01 UTC by Alexey
Modified: 2021-11-30 01:54 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
patch (file_605732.txt,691 bytes, patch)
2017-01-15 01:03 UTC, Alexey
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
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