I get this error when I try to run cargo-ebuild without http-parser installed, and it's not pulled in by cargo-ebuild. $ cargo-ebuild -h cargo-ebuild: error while loading shared libraries: libhttp_parser.so.2.9: cannot open shared object file: No such file or directory Reproducible: Always Steps to Reproduce: 1. emerge -C net-libs/http-parser 2. emerge -1 dev-util/cargo-ebuild 3. Run `cargo-ebuild` Actual Results: Does not run. Expected Results: Should run.
Hm, wonder where that came from. Mine isn't linked with http_parser and it doesn't seem to be automagic either (doesn't matter whether I have it installed or not), unless there's some other requirement to trigger it. What does lddtree /usr/bin/cargo-ebuild output?
I checked my PATH and it had ~/.cargo/bin and of course somehow cargo-ebuild got in there, not built from Portage. That was the one requesting http-parser be present. Invalid ticket.
Ah sneaky .cargo, thanks for re-checking.
yeah old cargo-ebuild used to depend on it (because it used full cargo as a library, which depends on http parser) you must have built it manually at some point =) new one does not, it uses cargo-metadata crate which does not even download anything.
