-
Notifications
You must be signed in to change notification settings - Fork 535
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
makeindex.exe: file not writable for security reasons #2416
Comments
See MiKTeX/miktex#178 (comment) See https://docs.miktex.org/manual/miktex.ini.html for |
@jlelong The difference might come from that we execute @Freguglia Could you confirm that executing the command with the absolute path in PowerShell fails?
|
The log says
|
Hum, this is the most recent one. |
The error message might come from: |
I confirm that the error is caused by using absolute paths, logs are pasted below.
I could build the project by removing the |
@Freguglia Thank you. |
Could you try to run the command from the directory You could also try adding the
I cannot reproduce the issue with the same version of
|
Adding
Doesn't |
@Freguglia you are right, |
I cannot reproduce the issue on GitHub Actions either: We had better add a test for this issue if possible. |
@tamuratak are you sure the GitHub Action uses |
By incrementing the LaTeX-Workshop/.github/workflows/texlive_on_linux.yml Lines 2 to 3 in f7a640f
You can see the version clicking
|
That may be related to the version of Perl module @Freguglia what is the output of perl -MCwd -e 'print $Cwd::VERSION."\n";' @tamuratak Can you add it to the github workflow? |
I have enabled the We can run only We can also call We can see the versions of commands: |
@Freguglia can you give the output of the followings commands run from
|
Hello, sorry for the delayed response, I had no Windows machine available for a couple of days. Here are the outputs of the commands:
I just realized I'm using the I'm just finishing my MikTex installation on this new box and to confirm the error persists (which should as I replicate the same steps to reproduce the error that occurred 3 times already), and then I'll try getting a new |
I've installed the latest version of Strawberry perl (5.32.0) and now I can compile using absolute paths. Thus the extension works with the default recipes. |
Great! We can finally close this issue! |
Preliminary questions [Required]
I'm having trouble building a project with the
latexmk
recipe in Windows regardingmakeindex
and apparent security problems when running it from the extension. I have little to no experience in Windows, so there is a chance I'm missing something silly here, but I've tried to search for similar problems and debug for a couple of days with no success now.Disable all the other extensions except for LaTeX Workshop, and check that you still see this issue. [Required]
You still see this issue?: Yes
Fresh VS Code install, only installed the LaTeX-Workshop extension
Make sure to visit the wiki FAQ before filling an issue.
You visited the wiki?: Yes
If your issue is with compiling a document (not having to do with finding the root file of a project), check first that you can compile manually.
You can compile a TeX document manually?: Yes
If I run the command equivalent to the standard recipe
latexmk -pdf -synctex=1 etc
in PowerShell the build completes without any errors.Describe the bug [Required]
latexmk
recipe fails to build, log says: "makeindex.exe: file not writable for security reasons
". I'm running Windows 10 and MikTex. Tried from a fresh Windows installation and got the exact same results.latexmk
works as expected when running from command line (PowerShell).Expected behavior
Using the
latexmk
recipe should successfully complete like when running from PowerShellLogs [Required]
Please paste the whole log messages here, not parts of ones. The log should start with
Initializing LaTeX Workshop
. It is very important to identify problems.LaTeX Workshop Output [Required]
Developer Tools Console [Required]
Nothing suspicious.
Desktop [Required]
Additional questions
Are you using VSCodium?
No
Are you using LaTeX Workshop with VS Code Remote?
No
Additional context
Works as expected in Linux.
The text was updated successfully, but these errors were encountered: