From: ralfconn <mentadent47@yahoo.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Emerge trouble with firefox and thunderbird ...
Date: Sun, 10 Mar 2024 20:43:46 +0100 [thread overview]
Message-ID: <6c73956b-82cf-49cc-82eb-a41d2d0ee9b9@yahoo.com> (raw)
In-Reply-To: <2733741.mvXUDI8C0e@cube>
Il 10/03/24 15:08, Peter Humphrey ha scritto:
> On Sunday, 10 March 2024 07:17:27 GMT Walter Dnes wrote:
>
>> So there are at least 2 people who've found out that Firefox can and
>> *MUST* be built with USE="-clang".
> Ah. I'll change my USE flag straight away.
>
> Thanks Walter.
This got me wondering, here I don't have clang in my make.config. The
main packages using it are:
[I] www-client/firefox
Installed versions: 123.0.1(rapid)(21:16:32 03/06/24)(X clang ...
[I] mail-client/thunderbird
Installed versions: 115.8.1(21:14:19 03/07/24)(X clang ...
[I] app-office/libreoffice
Installed versions: 7.6.5.2^t(21:42:53 03/06/24)(... -clang ...
libreoffice sees it unset because it is not present in the global uses.
firefox and thunderbird instead set it in the ebuild:
$ grep clang /var/db/repos/gentoo/www-client/firefox/firefox-123.0.ebuild
IUSE="+clang cpu_flags_arm_neon dbus debug eme-free hardened hwaccel"
$ grep clang
/var/db/repos/gentoo/mail-client/thunderbird/thunderbird-115.8.1.ebuild
IUSE="+clang cpu_flags_arm_neon dbus debug eme-free hardened hwaccel"
Both packages have no issues here with +clang. Given the warning message
reported by Peter ("Enable USE=clang unless you have a very good reason
not to.") and the fact that gentoo developers decided to switch it on
specifically for these packages it would probably be a better idea to
file a bugzilla rather than forcing the use of GCC, which might fix the
issue now but lead to problems later. As usual, YMMV.
raf
next prev parent reply other threads:[~2024-03-10 19:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-03 9:47 [gentoo-user] Emerge trouble with firefox and thunderbird Wols Lists
2024-03-03 18:54 ` Wols Lists
2024-03-03 19:40 ` Jack
2024-03-03 20:23 ` Wol
2024-03-03 21:18 ` Jack
2024-03-03 23:13 ` Carsten Hauck
2024-03-09 8:04 ` Wols Lists
2024-03-09 12:49 ` Walter Dnes
2024-03-09 14:45 ` Peter Humphrey
2024-03-09 19:37 ` Walter Dnes
2024-03-09 21:16 ` Peter Humphrey
2024-03-10 7:17 ` Walter Dnes
2024-03-10 14:08 ` Peter Humphrey
2024-03-10 19:43 ` ralfconn [this message]
2024-03-10 22:44 ` Walter Dnes
2024-03-11 18:25 ` ralfconn
2024-03-10 13:50 ` [gentoo-user] " mp666
2024-03-10 22:44 ` Carsten Hauck
2024-03-11 7:39 ` Wols Lists
2024-03-04 16:20 ` [gentoo-user] " ralfconn
2024-03-06 8:22 ` Wols Lists
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6c73956b-82cf-49cc-82eb-a41d2d0ee9b9@yahoo.com \
--to=mentadent47@yahoo.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox