From: Marco Rebhan <me@dblsaiko.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Firefox and clang
Date: Fri, 01 Nov 2024 18:00:20 +0100 [thread overview]
Message-ID: <5861349.DvuYhMxLoT@invader> (raw)
In-Reply-To: <115370864.nniJfEyVGO@rogueboard>
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
On Friday, 1 November 2024 17:41:25 CET Michael wrote:
> 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.
Hi Michael,
https://bugs.gentoo.org/941878 seems to be the relevant bug with discussion on
why it was changed.
> PS. Also I do not understand the meaning of these notations:
>
> IUSE="foo"
Everything outside the quotes is normal bash syntax, the variable contents are
interpreted by Portage.
This sets the ebuild to have USE flags "foo". (If IUSE was set before this
line, it will clear out all the USE flags that were defined before.)
> IUSE="+foo"
This sets the ebuild to have USE flags "foo", the preceding "+" on the USE
flag means it is enabled by default.
> IUSE+="foo"
This appends to the previous IUSE value. Equivalent to IUSE="${IUSE}foo" (note
the missing space, hence why the Firefox ebuild uses IUSE+=" foo" instead).
Cheers,
Marco
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-01 17:00 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
2024-11-01 17:00 ` Marco Rebhan [this message]
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=5861349.DvuYhMxLoT@invader \
--to=me@dblsaiko.net \
--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