-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
c2v error #11
Comments
It's better to use Make sure to v up. |
I did git clone and got a out put: |
I have the exact same issues as you.
I think this is caused by a wrong implementation of |
See vlang/v#14835 |
I think this issue has been fixed and can be closed. |
@AnimalStudioOfficial Hi. Can you please confirm that error is gone? |
I'm closing this issue since no response from the author and @Wertzui123 fixed the similar issue |
OS: windows, Microsoft Windows 11 Home v22000 64-bit
Processor: 4 cpus, 64bit, little endian, Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz
CC version: cc (Rev10, Built by MSYS2 project) 11.2.0
getwd: C:\Users\Dragon boy\Downloads\c2v-master\c2v-master
vmodules: C:\Users\Dragon boy.vmodules
vroot: C:\v-master\v-master\v
vexe: C:\v-master\v-master\v\v.exe
vexe mtime: 2022-06-22 19:22:13
is vroot writable: true
is vmodules writable: true
V full version: V 0.2.4 e6c3de2.c9ab086
Git version: git version 2.24.1.windows.2
Git vroot status: weekly.2022.24-63-gc9ab0860 (1 commit(s) behind V master)
.git/config present: true
thirdparty/tcc status: thirdparty-windows-amd64 125e21e2
What did you do?
$ ./c2v-master for.c
What did you expect to see?
What did you see instead?
V panic: cannot find clang in PATH
v hash: c9ab086
C:/Users/Dragon boy/AppData/Local/Temp/v_0/c2v-master.1673194596058845405.tmp.c:10921: at _v_panic: Backtrace
C:/Users/Dragon boy/AppData/Local/Temp/v_0/c2v-master.1673194596058845405.tmp.c:28465: by main__find_clang_in_path
C:/Users/Dragon boy/AppData/Local/Temp/v_0/c2v-master.1673194596058845405.tmp.c:32730: by _vinit
C:/Users/Dragon boy/AppData/Local/Temp/v_0/c2v-master.1673194596058845405.tmp.c:32750: by wmain
00569678 : by ???
005697db : by ???
7ffab40754e0 : by ???
The text was updated successfully, but these errors were encountered: