Running cargo-ebuild ebuild --noaudit in the cloned https://github.com/rust-lang/rust-bindgen.git repo with tag v0.63.0 checked-out causes cargo-ebuild to hang indefinitely without producing any output.
If I run it through ltrace, I see:
[pid 18249] SYS_write(2, "waiting for file lock on package"..., 38 <unfinished ...>
[pid 18248] SYS_read(6 <unfinished ...>
[pid 18249] <... SYS_write resumed> ) = 38 <0.000063>
[pid 18248] <... SYS_read resumed> , "waiting for file lo", 19) = 19 <0.000024>
[pid 18249] SYS_write(2, "\n", 1 <unfinished ...>
[pid 18248] SYS_read(6 <unfinished ...>
[pid 18249] <... SYS_write resumed> ) = 1 <0.000029>
[pid 18248] <... SYS_read resumed> , "ck on package cache\n", 32) = 20 <0.000026>
[pid 18249] SYS_flock(3, 2, 1, 0x7e8b5237b929f181 <unfinished ...>
[pid 18248] SYS_read(6 <no return ...>
error: maximum array length seems negative
, "", 12) = -11 <0.000016>
[pid 18248] SYS_poll(0x7ffdaff412d8, 2, -1
… whereupon it hangs until interrupted. This happens with releases 0.5.1 & 0.5.2.
It would be handy if a --verbose option could be added to give more visibility into what is happening internally (what files are being read, what crates have been discovered on the fly, etc.)!
Running
cargo-ebuild ebuild --noauditin the cloned https://github.com/rust-lang/rust-bindgen.git repo with tag v0.63.0 checked-out causescargo-ebuildto hang indefinitely without producing any output.If I run it through
ltrace, I see:… whereupon it hangs until interrupted. This happens with releases 0.5.1 & 0.5.2.
It would be handy if a
--verboseoption could be added to give more visibility into what is happening internally (what files are being read, what crates have been discovered on the fly, etc.)!