public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Firefox fails to compile. crc32 error??
Date: Thu, 23 Nov 2023 02:08:47 -0600	[thread overview]
Message-ID: <189d7826-e07e-94b4-28f0-27bf78b0e869@gmail.com> (raw)
In-Reply-To: <868f0a5c-ad21-41d3-b691-11466eacdf7a@gentoo.org>

Daniel Pielmeier wrote:
> Looks like it is related to -march=native.
>
> See bug https://bugs.gentoo.org/838373
>


Nailed it.  After the post by Michael, I edited the kernel several
times.  I'm sure I ruled that thing out.  I had some crc stuff not there
but same error with or without.  I admit, I wouldn't have thought of a
kernel driver issue but the error did sort of lead that way.  Given the
CPU FLAGS is about the CPU and its instruction set, it could be a option. 

I would never have thought of the CFLAGS in make.conf.  I'm not sure how
you figured that out either.  o_O  Before trying new settings for that,
I tried newer versions of clang, llvm and their friends to see if there
was a fix that wasn't applied to older versions.  When you unmask one
thing, it snowballs a bit.  Anyway, after getting a more recent version
of clang and llvm, it still failed.  At that point, I suspected that I
had ruled out those packages.  I did some digging to find what my CFLAG
settings should be if done manually.  It took some digging tho.  Once I
set that to the manual way, it compiled successfully on the first try. 

So, my backup rig now has a web browser.  That's good.  ;-)  I wonder
why that bug report wasn't in the search results when I was digging for
the error???  If I see something Gentoo related, I always look. 

While at it.  I don't think there is a way but I may have missed it.  As
a example, when I wanted to unmask/keyword specific versions of llvm and
clang, is there a tool to find out what all else has to also be
unmasked/keyworded?  When I tried to do that for the packages I wanted,
I ended up running emerge to find more that had to be added to the
list.  This is the list I ended up with. 


sys-devel/clang
sys-devel/llvm
sys-devel/clang-common
sys-devel/clang-runtime
sys-devel/clang-toolchain-symlinks
sys-libs/compiler-rt
sys-libs/compiler-rt-sanitizers
sys-libs/libomp
sys-devel/llvm-toolchain-symlinks
sys-devel/llvmgold



It would be nice if there is a way to just run a command once and it
spits out a friendly list that can be added to the proper file.  Save
annoying some electrons and all.  ;-) 

Thanks much to you both.  I hope if someone else runs into this, this
thread pops up in the search results.  Save someone some head scratching. 

Dale

:-)  :-) 

P. S.  Switched computer case door to left side hinge the other day. 
Put in the drive trays and figuring out if there is a way to put drives
in other places and still have lots of fans.  :-D 


  reply	other threads:[~2023-11-23  8:08 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
2023-11-22 18:44 ` Daniel Pielmeier
2023-11-23  8:08   ` Dale [this message]
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=189d7826-e07e-94b4-28f0-27bf78b0e869@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