-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Building 0.4.6 release: V panic: No such file or directory; code: 2
#21667
Comments
Build your V executable without |
Those are 2 separate commands, implemented in 2 separate programs. Just do |
Thank you! At least I got some better output.
|
@bberberov have you checked the |
|
V in unpacked from the release source tarball.
The
|
Normally, the tools are built the first time they're used, but you have to have a successful build of V for that to happen... and it's probably not something you want in a package, anyway. One of the many reasons I keep saying it is far too soon to make official packages for V. Cloning and building the source is the bests/most reliable method for now. |
Why are you setting If it is not set, then V will try to set it itself, by looking at the path of the currently running Imho what is happening, is that you are setting it to a folder, that is not containing the cmd/tools and its sources, then when V tries to locate them, it fails. |
I think that you may be better off building everything in the same folder, and then copy only what you need from it. That will eliminate such problems. i.e. try commenting or moving the The other |
You are absolutely right; that was it. 🤦 Thanks! Now I'm getting an error I expect, and need to work on, since there is no
I'm not making an official package. OBS just does a great job of setting up a build environment. |
tcc should be a recent one (the one most distros provide is We do supply a prebuilt tcc executable in See https://github.com/vlang/tccbin/blob/thirdparty-linux-amd64/README.md if you want to rebuild it on your own for amd64. |
|
I looked into it earlier, and I have a I found |
Describe the bug
I'm trying to build/package the 0.4.6 release of V on openSUSE. I'm following packaging_v_for_distributions.md It appears I can produce a
v
binary and I'm trying to dov build-tools
. That was failing, so I triedv self-test
. I'm getting this error:It does not give me enough information to proceed further. Is there a way to figure out what file it cannot find?
Reproduction Steps
Here is the project with the
.spec
file if that can be helpful:https://build.opensuse.org/package/show/home:bberberov/vlang
Expected Behavior
A more verbose output so I can figure out what is missing and correct it.
Current Behavior
Possible Solution
No response
Additional Information/Context
No response
V version
0.4.6
Environment details (OS name and version, etc.)
If I cannot run
self-test
can I rundoctor
? I didn't even know that existed until now.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.
The text was updated successfully, but these errors were encountered: