-
Notifications
You must be signed in to change notification settings - Fork 161
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
cargo install tectonic
failed to run custom build command for tectonic_bridge_harfbuzz v0.2.9
#1172
Comments
tectonic_bridge_harfbuzz v0.2.9
"tectonic_bridge_harfbuzz v0.2.9
tectonic_bridge_harfbuzz v0.2.9
ecargo install tectonic
failed to run custom build command for tectonic_bridge_harfbuzz v0.2.9
ecargo install tectonic
failed to run custom build command for tectonic_bridge_harfbuzz v0.2.9
cargo install tectonic
failed to run custom build command for tectonic_bridge_harfbuzz v0.2.9
Little addition: When using tectonic as a dependency, I get the same error from
Therefore, the issue is likely related to the vendoring of harfbuzz. |
Ran into the same error just now on a Kali (Debian-based) system (rolling release; updated just prior) where the same tectonic version (0.15.0) was being reinstalled ( Uninstalling and installing fresh did not resolve it. Based on your observation adding the |
I believe this might be fixed in #1156 which has not yet made it to a crates.io release. I was able to successfully build by specifying a git dependency in my Cargo.toml:
|
I have the same problem when trying to install tectonic on Ubuntu 24.04 beta with:
If instead I use
It works fine. I guess a lot of people will hit this problem when Ubuntu 24.04 is released in a week or so, so maybe it makes sense to cut a release. |
I tried to install tectonic via
cargo install tectonic
.Unfortunately, it failed with the following error message.
I'm using Ubuntu 22.04 and my installed libharfbuzz-dev version is
I installed all dependencies via
Please help me to understand what is going wrong.
The text was updated successfully, but these errors were encountered: