From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox fails to compile. crc32 error??
Date: Wed, 22 Nov 2023 12:04:39 -0600 [thread overview]
Message-ID: <6625d13d-4a66-757f-6af4-a3500d02ef37@gmail.com> (raw)
In-Reply-To: <13396426.uLZWGnKmhe@rogueboard>
Michael wrote:
> On Wednesday, 22 November 2023 02:27:01 GMT Dale wrote:
>> Howdy,
>>
>> I decided to set up the 770T as a backup system. I'm installing the
>> basics that I would need to get started. The water heater set back my
>> new build a bit. Anyway, Firefox fails to build with something about a
>> missing crc32. I found a package with that name and installed it,
>> thought maybe the ebuild was missing a depend or something, still
>> fails.
> You are probably missing a number of CRC modules in your kernel, rather than
> the Google library which you emerged.
I figured that package I emerged was a long shot. I went into the
kernel config and enabled everything crc32 I could find. It still
fails. I changed one, since it has 4 options but can only enable one at
a time, and am trying again. I don't know if this is going to work or
not. It's chewing on it. It's cool here so the heat helps a little. lol
Does anyone know exactly what kernel driver it wants? Also, when it
runs its pre-emerge checks, why doesn't it see that it is missing and
fail with the info on what is missing? Why wait until it fails, about
90% of the way through the compile process, and then spit out a error
that isn't really helpful???? This a bug maybe???
Jeepers. ;-)
Dale
:-) :-)
next prev parent reply other threads:[~2023-11-22 18:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 2:27 [gentoo-user] Firefox fails to compile. crc32 error?? Dale
2023-11-22 8:53 ` Michael
2023-11-22 18:04 ` Dale [this message]
2023-11-22 18:44 ` Daniel Pielmeier
2023-11-23 8:08 ` Dale
2023-11-23 11:06 ` Daniel Pielmeier
2023-11-23 11:31 ` Michael
2023-11-23 20:17 ` Dale
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=6625d13d-4a66-757f-6af4-a3500d02ef37@gmail.com \
--to=rdalek1967@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