public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Carsten Hauck <zem42@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Emerge trouble with firefox and thunderbird ...
Date: Mon, 4 Mar 2024 00:13:12 +0100	[thread overview]
Message-ID: <20240303231312.buwhxxzwgs225yrf@imaps.gmx.net> (raw)
In-Reply-To: <GEKQRLMF.YS6NTVE6.AP2ZT2OA@RRZINVBQ.MMTXEOQU.O2IPUX7C>

On 03/03/24 at 04:18, Jack wrote:
>On 2024.03.03 15:23, Wol wrote:
>>On 03/03/2024 19:40, Jack wrote:
>>>On 2024.03.03 13:54, Wols Lists wrote:
>>>>On 03/03/2024 09:47, Wols Lists wrote:
>>>>>I'm getting this output from
>>>>>
>>>>>emerge --update --newuse --deep --with-bdeps=y @world
>>>>
>>>>whoops I mean "emerge --depclean"
>>>>
>>>>I'm trying to get a clean system, and don't know what exactly is
>>>>wrong, or what to try ...
>>>>
>>>>Cheers,
>>>>Wol
>>>>
>>>As the error says, you generally need to do a full update before
>>>you can depclean.
>>>
>>>What error(s) do you get when trying to update firefox or
>>>thunderbird?  What happens if you try to update @world?
>>>
>>Both firefox and thunderbird seemed to die for no obvious reason.
>>Where do I find the logs?
>>
>>But because depclean complained, I did blah-blah-with-bdeps, which
>>emerged (or tried to) 21 packages, but firefox/thunderbird still
>>bombed, and then --depclean still complained.
>>
>>So I don't know what's going on, but basically Mozilla won't emerge,
>>and I don't know why ...
>>
>>Cheers,
>>Wol
>Did the other 19 package emerge OK?  Are the mozilla progs crashing
>when running, or when emerging?  If emerging, the log is just console
>output, as indecipherable as we know it sometimes can be.  If they
>crash when running, try running from command line.
>

Some time ago on one of my machines Thunderbird and Firefox stopped to
compile with USE="clang". As they can be build with gcc I never digged
too deep into that problem but maybe it's worth a shot.

Greetings,
Carsten


  reply	other threads:[~2024-03-03 23:13 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 [this message]
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
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=20240303231312.buwhxxzwgs225yrf@imaps.gmx.net \
    --to=zem42@gmx.de \
    --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