I don’t recall adding or removing any repos in my pacman.conf to install any packages. 
Please show the output of these commands:
pacman -Qo gcc
type gcc
echo $CC
sudo journalctl -b -0 | grep gcc
which -a gcc
You likely have installed the conda gcc from the net. It is better to get rid of it unless you know you need it for something.
Tip: always prefer native Archlinux & EndeavourOS packages. Only if native packages are not available and you really need more, then use the AUR.
1 Like
pacman -Qo gcc:
error: No package owns /home/zer0svoid/anaconda3/bin/gcc
type gcc:
gcc is /home/zer0svoid/anaconda3/bin/gcc
echo $CC: no output
sudo journalctl -b -0 | grep gcc:
May 25 18:24:47 voidbox kernel: Linux version 6.8.9-arch1-2 (linux@archlinux) (gcc (GCC) 14.1.1 20240507, GNU ld (GNU Binutils) 2.42.0) #1 SMP PREEMPT_DYNAMIC Tue, 07 May 2024 21:35:54 +000
which -a gcc:
/home/zer0svoid/anaconda3/bin/gcc
/usr/bin/gcc
Yeah, I can’t recall what I used it for. I vaguely remember using it for something, but it’s really escaping me. How do I go about removing this package?
Yep. You somehow installed it manually, but don’t remember. Here’s how it should look:
pacman -Qo gcc
/usr/bin/gcc is owned by gcc 14.1.1+r58+gfc9fb69ad62-1
Notice the path?
Not sure if this has been tried already, but what’s the output of the command below?
sudo pacman -Syu gcc
You can also try just -Sy.
Ah, I there’s no owner on my end and that it only checks on the anaconda version.
When I try updating gcc with pacman -Sy gcc, I’m told that it is up to date and I’d be reinstalling.
I noticed, and that’s the problem.
Please show the output.
Sure thing
:: Synchronizing package databases...
endeavouros is up to date
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: gcc-14.1.1+r58+gfc9fb69ad62-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Package (1) Old Version New Version Net Change
core/gcc 14.1.1+r58+gfc9fb69ad62-1 14.1.1+r58+gfc9fb69ad62-1 0.00 MiB
Total Installed Size: 201.62 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
Try renaming this folder to /home/zer0svoid/anaconda3-bak then try to boot from the kernel. It’s unlikely to work, so you’ll probably have to restart with CTRL+ALT+DEL. But worth a shot.
Before that, please show the output of:
la /home/zer0svoid/anaconda3/
ls /home/zer0svoid/anaconda3/ gives me
bin envs libexec pkgs share x86_64-conda_cos6-linux-gnu pyodbc.pyi
compiler_compat etc licensing plugins shell x86_64-conda-linux-gnu
condabin include man qml ssl conda.exe
conda-meta install_tmp mkspecs resources translations LICENSE.txt
doc lib phrasebooks sbin var postconda.tar.bz2
la not ls, please.
Also, one of these folders should have a file(s) with instructions on how to uninstall it.
My apologies, I assumed ls because with la bash tells me the it can’t find that command.
I see. 
Well, back to this, then:
and this:
I will have to do some digging to find how to uninstall anaconda.
On the side of renaming the folder /home/zer0svoid/anaconda3-bak I was able to install the new kernel without the errors I was unfamiliar with I mentioned earlier.
Error! Bad return status for module build on kernel: 6.9.1-arch1-1 (x86_64)
WARNING: errors were encountered during the build. The image may not be complete.
Booted into the kernel without issue.
checking ownership of gcc seems normal as well
pacman -Qo gcc
/usr/bin/gcc is owned by gcc 14.1.1+r58+gfc9fb69ad62-1
1 Like
I really didn’t expect that to work… Well, case closed, then? Hooray?
2 Likes
By the way, does your PATH variable contain the anaconda folder? If so, better remove that from tve PATH.
2 Likes
I’m quite surprised that was the solution as well!
I have have it as a PATH, it’s been removed.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.