alacritty: fails to install from git

cargo install --git https://github.com/jwilm/alacritty/ --force

    Updating git repository `https://github.com/jwilm/alacritty/`
  Installing alacritty v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)
    Updating crates.io index
error: failed to compile `alacritty v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)`, intermediate artifacts can be found at `/tmp/cargo-installnMe4iJ`

Caused by:
  multiple packages link to native library `freetype`, but a native library can be linked only once

package `freetype-sys v0.7.1`
    ... which is depended on by `freetype-rs v0.19.1`
    ... which is depended on by `font v0.1.0 (https://github.com/jwilm/alacritty/#37b66a7c)`
    ... which is depended on by `alacritty_terminal v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)`
    ... which is depended on by `alacritty v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)`
links to native library `freetype`

package `servo-freetype-sys v4.0.3`
    ... which is depended on by `servo-fontconfig-sys v4.0.7`
    ... which is depended on by `servo-fontconfig v0.4.0`
    ... which is depended on by `font v0.1.0 (https://github.com/jwilm/alacritty/#37b66a7c)`
    ... which is depended on by `alacritty_terminal v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)`
    ... which is depended on by `alacritty v0.3.2 (https://github.com/jwilm/alacritty/#37b66a7c)`
also links to native library `freetype`

Running cargo build --release in the repo does not show the failure though. 🤔

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 13
Comments: 15 (12 by maintainers)

Most upvoted comments

Yeah I missed it but found it by myself while searching the cargo issue tracker. Both cargo and rustup could definitely benefit from some more attention

NickeZ on May 2, 2019

I’m not fond of keeping track of when exactly things are stabilized. The bug has been fixed and people interested in installing through git can use nightly until it works in stable. Alacritty’s issue tracker isn’t here to keep track of Rust feature stabilizations and it would be quite difficult to do that. So I’d rather close this now and be done with it rather than keeping it open for no purpose and forgetting about it.

chrisduerr on Jan 27, 2020

Looks like someone has fixed this in cargo: https://github.com/rust-lang/cargo/pull/7768.

chrisduerr on Jan 27, 2020