[info] and incase helps others (is now working)

[splace]

trying update, fine 4 weeks ago...

> v up
==================
tcc: error: library 'atomic' not found
...
==================
(Use `v -cg` to print the entire error message)

builder error: 
==================
C error found. It should never happen, when compiling pure V code.
This is a V compiler bug, please report it using `v bug file.v`,
or goto https://github.com/vlang/v/issues/new/choose .
You can also use #help on Discord: https://discord.gg/vlang .

same for

v upgrade

v update

v outdated

v list

but.....

v self

worked and seemed to fix, was able to perform all previously failing commands.

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

[spytheman]

On what OS/platform?

Can you please paste the output of v doctor ?

[splace]

i imagined there was some 'state' that was unanticipated, but when fixed, unfortunately, any info about the 'state' was probably lost.

hence this report, to be found if happens again to anyone.

simon@fedora:~/v$ ./v doctor
V full version: V 0.4.5 0073059.9639f55
OS: linux, Linux version 6.9.0-64.fc41.x86_64 (mockbuild@adafb04285ef452d9a9962fcd3e624c1) (gcc (GCC) 14.1.1 20240507 (Red Hat 14.1.1-1), GNU ld version 2.42.50.20240318) #1 SMP PREEMPT_DYNAMIC Mon May 13 11:58:46 UTC 2024
Processor: 2 cpus, 64bit, little endian, Intel(R) Core(TM)2 Duo CPU     E8300  @ 2.83GHz

getwd: /var/home/simon/v
vexe: /var/home/simon/v/v
vexe mtime: 2024-05-16 17:29:11

vroot: OK, value: /var/home/simon/v
VMODULES: OK, value: /var/home/simon/.vmodules
VTMP: OK, value: /tmp/v_1000

Git version: git version 2.45.1
Git vroot status: weekly.2024.20-2-g9639f55d-dirty (55 commit(s) behind V master)
.git/config present: true

CC version: cc (GCC) 14.1.1 20240507 (Red Hat 14.1.1-1)
thirdparty/tcc status: thirdparty-linux-amd64 40e5cbb5