Open ThisNekoGuy opened 2 years ago
Doesn't that just add it to /usr/bin/
?
The fact that v help
(you don't need the --
in front of help
) works says V is being found. The problem is that it isn't telling you what wasn't found when you try to run v doctor
.
Also, running sudo/doas v symlink
didn't solve it:
neko-san@ARCH /m/e/test> doas v symlink
doas (neko-san@ARCH) password:
neko-san@ARCH /m/e/test> v doctor
V panic: No such file or directory
v hash: 0e1cfd4
addr2line: 'v': No such file
v(+0x1642ba) [0x55f864fcb2ba]
addr2line: 'v': No such file
v(+0x2072) [0x55f864e69072]
| 0x7f2ac907bb25 | /usr/lib/libc.so.6(__libc_start_main+0xd5)
addr2line: 'v': No such file
v(+0x20ae) [0x55f864e690ae]
neko-san@ARCH /m/e/test [1]>
Should be fine now. Please try again @ThisNekoGuy
@medvednikov
It works; I made an Arch Linux repository that installs V releases as a alpm package:
https://gitlab.com/N3k0-san/vlang-latest.sh
(I'm new to git
though)
the result of v doctor
is now this:
neko-san@ARCH ~> v doctor
OS: linux, "Arch Linux"
Processor: 16 cpus, 64bit, little endian, AMD Ryzen 7 3700X 8-Core Processor
CC version: cc (GCC) 12.1.0
getwd: /home/neko-san
vmodules: /home/neko-san/.vmodules
vroot: /usr/lib/vlang
vexe: /usr/lib/vlang/v
vexe mtime: 2022-07-11 23:32:58
is vroot writable: false
is vmodules writable: true
V full version: V 0.3.0 dc68469
Git version: git version 2.37.0
Git vroot status: Error: fatal: not a git repository (or any of the parent directories): .git
.git/config present: false
thirdparty/tcc status: Error: fatal: unsafe repository ('/usr/lib/vlang/thirdparty/tcc' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /usr/lib/vlang/thirdparty/tcc
Error: fatal: unsafe repository ('/usr/lib/vlang/thirdparty/tcc' is owned by someone else)
To add an exception for this directory, call:
git config --global --add safe.directory /usr/lib/vlang/thirdparty/tcc
neko-san@ARCH ~>
How are you installing V? From a .zip file?
The preferred method is to git clone
the source, then run make
. Otherwise, you'll see the git failures.
Also, the V install dir should also be writeable by you. Installing it as root or other privileged user will cause the tcc error you saw.
Simply put, what it does is run a sub-script that updates an Arch Linux PKGBUILD file that pulls the latest release source from the releases page here, compiles it with make
, then installs it globally for every user on the system. It's essentially like installing something from the AUR; the only difference here is that the associated files involved aren't officially on the AUR, but from my gitlab repo.
I'm aware of the issue about the user permissions but the AUR "method" of installation doesn't really have a solution for that. You can sort of look at this like a "dry run" of what it would look like if it were an AUR package.
... and that's one of the reasons there are no official packages, yet. Until issues like that are dealt with, there are too many problems if you don't git clone the source yourself to a directory where you have write permissions.
I didn't say anything about personally having a problem about it; I was only clarifying what I did because you asked
This is a 7 month old version of V. Try with the latest one.
This is a 7 month old version of V. Try with the latest one.
0.3 is from 13 days ago; what are you talking about?
Sorry, I was looking at the first post.
Are you still having this issue?
V version:
0.2.4 0e1cfd4
(weekly.2021.52.1) OS: Arch LinuxWhat did you do? Run
v doctor
after installing V with my own PKGBUILD that should have been fine; it compiles V from the latest release (namely "weekly.2021.52.1" in this occurrence) and avoids compiling with TCC entirely.vlang-latest.zip
(The "update.sh" is just an automated script I put together to easily detect latest releases and update the PKGBUILD and .SRCINFO for them and it also includes checksum validation.)
V was compiled with my global
/etc/makepkg.conf
configuration (I compiled with Clang, -O3, and LTO enabled):What did you expect to see? This information:
What did you see instead?