Summary: | www-client/firefox-105.0.2 - ERROR: www-client/firefox-105.0.2::gentoo failed (configure phase): | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Mozilla Gentoo Team <mozilla> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 870412 | ||
Attachments: |
emerge-info.txt
emerge-history.txt environment etc.portage.tar.bz2 logs.tar.bz2 temp.tar.bz2 www-client:firefox-105.0.2:20221005-041714.log |
Description
Toralf Förster
2022-10-05 07:29:35 UTC
Created attachment 820678 [details]
emerge-info.txt
Created attachment 820681 [details]
emerge-history.txt
Created attachment 820684 [details]
environment
Created attachment 820687 [details]
etc.portage.tar.bz2
Created attachment 820690 [details]
logs.tar.bz2
Created attachment 820693 [details]
temp.tar.bz2
Created attachment 820696 [details]
www-client:firefox-105.0.2:20221005-041714.log
I guess you're somehow forcing clang:15 to be used even when it's not supported by the ebuild yet. That's the mismatch happening in the log. (In reply to Joonas Niilola from comment #8) > I guess you're somehow forcing clang:15 to be used even when it's not > supported by the ebuild yet. That's the mismatch happening in the log. indeed, clang was forced this week, ok. BTW could the ebuild itself check before, whether gcc is used ? It should force gcc if "-clang" use flag is passed. But I imagine you can "break" it with custom rules. |