Skip to content
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

Texify / macOS: "The TeX engine could not be found." #149

Closed
brevilo opened this issue Jun 22, 2018 · 9 comments
Closed

Texify / macOS: "The TeX engine could not be found." #149

brevilo opened this issue Jun 22, 2018 · 9 comments
Assignees
Milestone

Comments

@brevilo
Copy link

brevilo commented Jun 22, 2018

Hi,

I'm running texify 2.9.6670 (MiKTeX 2.9.6700, first fresh install) on macOS 10.13.5 and always run into the following error:

2018-06-22 10:33:00,193+0200 INFO  texify - starting with command line: "/Applications/MiKTeX Console.app/Contents/bin/texify" --verbose --pdf --synctex=1 --clean file.tex
2018-06-22 10:33:00,324+0200 FATAL texify - The TeX engine could not be found.
2018-06-22 10:33:00,324+0200 FATAL texify - Info:
2018-06-22 10:33:00,324+0200 FATAL texify - Source: Programs/MiKTeX/texify/mcd.cpp
2018-06-22 10:33:00,324+0200 FATAL texify - Line: 1406

Interestingly running pdflatex, makeindex and bibtex themselves does work flawlessly. All three binaries are found by which in /usr/local/bin as expected. launchctl getenv PATH also returns /usr/local/bin as first component. Trying a private installation instead of a system-wide installation doesn't change anything. I'm really running out of ideas now.

Thanks

@brevilo
Copy link
Author

brevilo commented Jun 22, 2018

Update: tried to add --trace=access,core,files,filesearch,fndb but the output or log content didn't change. So where can I find the trace output?

@edocevoli edocevoli self-assigned this Jun 29, 2018
@edocevoli edocevoli added the bug label Jun 29, 2018
@edocevoli edocevoli added this to the 2.9.6800 milestone Jun 29, 2018
@anusha-potnuru
Copy link

anusha-potnuru commented Jul 22, 2018

Did you resolve it?
I am getting the same error.

@edocevoli
Copy link
Member

This will be fixed with the MiKTeX 2.9.6800 milestone.

@brevilo
Copy link
Author

brevilo commented Jul 26, 2018

Thanks!

@edocevoli
Copy link
Member

This will be fixed with milestone 2.9.6800.

@brevilo
Copy link
Author

brevilo commented Aug 23, 2018

Hi @edocevoli, this is really a pressing issue for us which could even mean to abandon MiKTeX which we'd like to avoid. In order to assess the options correctly, do you have a rough ETA on when you intend to release milestone 2.9.6800?

Thanks

@edocevoli
Copy link
Member

@brevilo: just follow the link...

@brevilo
Copy link
Author

brevilo commented Aug 24, 2018

Duh, thanks! 👍

@brevilo
Copy link
Author

brevilo commented Aug 27, 2018

FYI, just tried the latest release (miktex-2.9.6800-1-darwin-x86_64.dmg) and the issue is indeed fixed for me. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants