From: David Rosenbaum <rosenbaumd181@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Thunderbird build failure ..
Date: Sun, 1 Jan 2023 22:31:04 -0500 [thread overview]
Message-ID: <CAL+8heO+YfN+qEQ+cAidgkm1v1CabWnWjzN4vsnq74qvKqq7_A@mail.gmail.com> (raw)
In-Reply-To: <864b1773-ac74-9a7e-4e69-0e35a960fa7e@mail.meme.technology>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
Thanks bud
Dave
On Sun, Jan 1, 2023, 4:22 PM cal <cal@mail.meme.technology> wrote:
> On 1/1/23 13:05, Wol wrote:
> > On 01/01/2023 20:08, cal wrote:
> >> FWIW, Thunderbird builds fine with GCC on my machine -- I'm unsure of
> >> your reasons for setting your Portage compiler to clang, but you may
> >> wish to use a package.env override to build Thunderbird with GCC as a
> >> workaround until the problem can be fixed upstream.
> >
> > I don't know anything about clang ... it must be the default ...
> >
> > I thought part of Firefox/Thunderbird was written in Rust, so I assumed
> > it was built with llvm as a matter of course.
> >
> > I'll just wait for it to sort itself out.
> >
> > Cheers,
> > Wol
> You're right, it looks like the Thunderbird ebuild has a clang USE
> turned on by default; I didn't realize that in my earlier reply and
> assumed you had overridden this yourself. Regardless, this version
> built correctly on my machine, so it's worthy of investigation with
> upstream which combinations of parameters may be triggering the crash.
>
> cal
>
>
[-- Attachment #2: Type: text/html, Size: 1502 bytes --]
next prev parent reply other threads:[~2023-01-02 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-01 11:07 [gentoo-user] Thunderbird build failure Wols Lists
2023-01-01 18:33 ` cal
2023-01-01 19:14 ` Wols Lists
2023-01-01 20:08 ` cal
2023-01-01 21:05 ` Wol
2023-01-01 21:21 ` cal
2023-01-02 3:31 ` David Rosenbaum [this message]
2023-01-04 9:32 ` Dr Rainer Woitok
2023-01-16 10:01 ` [gentoo-user] Thunderbird build failure .. [Gone away] 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=CAL+8heO+YfN+qEQ+cAidgkm1v1CabWnWjzN4vsnq74qvKqq7_A@mail.gmail.com \
--to=rosenbaumd181@gmail.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