![]() The latest version of guest-additions on the Linux guest that I know works is 5.2.22. I have updated Virtualbox and extras on the Windows host to the latest version and still see the same issue. I'm not certain, but I suspect it has something to do with the Windows host, and not the Linux guest since I've tried running an identical VM on a Linux host and cannot re-create the issue there. I do not see this problem on normal (non-shared) folders on the guest. Since meson attempts to run the file instantly, it is still in this window when the file is not executable and fails. ![]() By printing file permissions from within the meson script, I found that when the file is originally created, it is not executable for some period of time (~500ms or so) before eventually becoming executable. Checking the generated file's permissions after the fact with ls -l shows that the file is actually executable. On newer base images, when it does this it fails with a file permission error that it cannot run the generated executable. To summarize that discussion: as part of the configuration process, meson wants to test the compiler tool chain to make sure it is callable and produces a working executable. I cannot post U R L's here, but see the meson google group for that discussion. At first, I though it was related to a new version of the build tool but after tracking it down with the meson team it is actually due to a permissions issue with the virtualbox shared folder. Recently, after updating to a newer vagrant base image, my build tool (meson) started failing. I have been putting my projects in a shared folder with the host to accomplish this. For the projects I'm working on, I also need to be able to work on the project files with some tools on the Windows host. ![]() I use Virtualbox (through Vagrant) to get a Linux development environment on a Windows Host. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |