3 ms·
Hello, Developer here. The release was messed up by me having serious git troubles. I had to destroy the repository twice, as the result and old README file wi
by amedvednikov 7y ago
Hello,
Developer here. The release was messed up by me having serious git troubles. I had to destroy the repository twice, as the result and old README file with the wrong instructions resulted in everyone having segfaults.
Everything will work as expected in a couple of days. Launching such a big project for hundreds (thousands?) of testers is not easy.
- sfilargi 7y agoIt’s just a toy project my friend. Stop marketing it as something extraordinary.
- faiface 7y agoSo, what are the correct instructions? I followed the instructions on the GitHub and yes, I'm getting segfaults.
- amedvednikov 7y agocan you `wget https://vlang.io/v.c` https://vlang.io/v.c` again?
- faiface 7y agoOkay, I did and I was able to compile the `vc` compiler from the C source. The REPL in `vc` seems to work (at least for the basic printing I tried) and running `./vc -o v .` worked as well. But the new `v` compiler segfaults with: coudlnt create file "/var/tmp/vlang0.0.12//vrepl.v" Segmentation fault (core dumped) EDIT: however, if I understand it correctly, it was not the instructions after all, that resulted in everyone having segfaults... EDIT2: okay, so I redownloaded the whole thing and yes, you fixed that now. But it still segfaults sometimes. For example if I try to pass a `-h` flag.
- amedvednikov 7y agoYou had to do `git pull` to fix the "V" V binary :) Forgot to mention that, sorry. It's going to be much, much more stable in the coming days.