public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael <confabulate@kintzios.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox and clang
Date: Fri, 01 Nov 2024 16:41:25 +0000	[thread overview]
Message-ID: <115370864.nniJfEyVGO@rogueboard> (raw)
In-Reply-To: <9d430c70-6900-4f59-b24e-d92b50cd03c7@users.sourceforge.net>

[-- Attachment #1: Type: text/plain, Size: 1963 bytes --]

On Friday 1 November 2024 14:43:17 GMT Jack Ostroff wrote:
> On 11/1/24 7:15 AM, Michael wrote:
> > Any idea why clang was disabled in www-client/firefox-128.4.0:
> > 
> > [ebuild     U  ] www-client/firefox-128.4.0:esr::gentoo
> > [128.3.1:esr::gentoo] USE="X dbus gmp-autoupdate hwaccel jumbo-build
> > openh264 system-av1 system- harfbuzz system-icu system-jpeg
> > system-libevent system-libvpx system-webp telemetry wayland -clang*
> > -debug -eme-free -gnome-shell -hardened -jack - libproxy -lto -pgo
> > -pulseaudio (-selinux) -sndio -system-png -wifi" L10N="en- GB -ach -af
> > -an -ar -ast -az -be -bg -bn -br -bs -ca -ca-valencia -cak -cs -cy -da
> > -de -dsb -el -en-CA -eo -es-AR -es-CL -es-ES -es-MX -et -eu -fa -ff -fi -
> > fr -fur -fy -ga -gd -gl -gn -gu -he -hi -hr -hsb -hu -hy -ia -id -is -it
> > -ja - ka -kab -kk -km -kn -ko -lij -lt -lv -mk -mr -ms -my -nb -ne -nl
> > -nn -oc -pa - pl -pt-BR -pt-PT -rm -ro -ru -sc -sco -si -sk -skr -sl -son
> > -sq -sr -sv -szl - ta -te -th -tl -tr -trs -uk -ur -uz -vi -xh -zh-CN
> > -zh-TW" LLVM_SLOT="18 -17 (-19)" 546,124 KiB
> > 
> > https://gitweb.gentoo.org/repo/gentoo.git/commit/?
> > id=75c0bdfd0b02568466c14d81aa0027c873a76617
> 
> Unless I miss something, I don't see evidence of that in the ebuilds. 
> It looks like IUSE has changed from +clang to just clang in the latest
> ebuilds in both slots.  Is it possible there is something else in your
> make.conf or packages.* which disables it? Actually, it might be that
> you need to explicitly add clang to packages.use, as not it is still
> allowed, but does not default to on.

I've checked and I have no bespoke directives for USE="clang".  Emerge will 
use whatever is the default setting for this flag.

Without USE="clang" the emerge takes 12-18% longer, but I am not sure what is 
the recommended compiler for FF or why it was changed.

PS. Also I do not understand the meaning of these notations:

IUSE="foo"
IUSE="+foo"
IUSE+="foo"

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-11-01 16:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 11:15 [gentoo-user] Firefox and clang Michael
2024-11-01 14:43 ` [gentoo-user] " Jack Ostroff
2024-11-01 16:41   ` Michael [this message]
2024-11-01 17:00     ` Marco Rebhan
2024-11-01 17:50       ` Michael
2024-11-01 18:08         ` Jack
2024-11-04  7:27         ` Wols Lists
2024-11-04 15:12           ` Philip Webb
2024-11-01 18:05     ` Jack

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=115370864.nniJfEyVGO@rogueboard \
    --to=confabulate@kintzios.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