public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Sopka <psopka@sopka.ch>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] System crash on "Detecting C compiler ABI info"
Date: Fri, 5 Apr 2024 08:34:01 +0200	[thread overview]
Message-ID: <a9f84647-742b-405c-81d0-6535c6a01331@sopka.ch> (raw)
In-Reply-To: <cbbfad6d-245f-4e5c-b0bc-317e3551ebfa@sopka.ch>

On 05.04.24 08:31, Paul Sopka wrote:
> On 05.04.24 00:55, Michael wrote:
>> Your toolchain is now correct.  Can you show the output of:
>>
>> equery u media-libs/libjpeg-turbo
>>
>> and
>>
>> emerge --info media-libs/libjpeg-turbo
>>
>> However, it could be this is a bug, you can check here for reports:
>>
>> https://bugs.gentoo.org/buglist.cgi?quicksearch=media-libs%2Flibjpeg-turbo 
>>
>>
>> If this is the only package you're getting a problem with, you can run:
>>
>> emerge --resume --skipfirst
>>
>> to complete your migration to profile 23.0, then try again to emerge 
>> libjpeg-
>> turbo on its own.
Also one or two weeks ago I successfully emerged with emptytree after 
migrating to profile 23.0.


  reply	other threads:[~2024-04-05  6:34 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 14:11 [gentoo-user] System crash on "Detecting C compiler ABI info" Paul Sopka
2024-04-02 18:50 ` J. Roeleveld
2024-04-02 19:43   ` Paul Sopka
2024-04-03  5:24     ` Paul Sopka
2024-04-03  7:40       ` Michael
2024-04-03 18:20         ` Paul Sopka
2024-04-03 22:44           ` Michael
2024-04-04 20:17             ` Paul Sopka
2024-04-04 20:32             ` Paul Sopka
2024-04-04 22:55               ` Michael
2024-04-05  6:31                 ` Paul Sopka
2024-04-05  6:34                   ` Paul Sopka [this message]
2024-04-05  9:01                     ` Michael
2024-04-08  6:29                       ` Paul Sopka
2024-04-03 12:44       ` James Massa

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=a9f84647-742b-405c-81d0-6535c6a01331@sopka.ch \
    --to=psopka@sopka.ch \
    --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