Age | Commit message (Collapse) | Author |
|
This appears to be an internal rust thing: I don't know why it's
leaking. We should investigate further.
|
|
We'd like to feature gate code that calls C from Rust, as a workaround
to several linker issues when running `cargo test` (#25386), and we
can't feature gate anything out of test code if `cargo test` is called
with `--all-features`.
* FIXES #26400: https://bugs.torproject.org/26400
|
|
The fix here is use a different bourne shell subsitution for
CARGO_ONLINE, so that an empty string counts as set.
|
|
Also make sure that we're actually running the test from within the right
cwd, like we do when we're building. This seems necessary to avoid
an error when running offline.
Amusingly, it appears that we had this bug before: we just weren't
noticing it, because of bug 26258.
|
|
Exit codes from find(1) seem not to be so reliable as we had hoped.
Closes ticket 26258; bugfix on 0.3.3.4-alpha when we fixed #25560
|
|
* FIXES #25560: https://bugs.torproject.org/25560.
|
|
Instead of using the cwd to specify the location of Cargo.toml, we
use the --manifest-path option to specify its location explicitly.
This works around the bug that isis diagnosed on our jenkins builds.
|
|
(This is just a matter of making sure that we handle the case where
abs_top_builddir is not set)
|
|
|
|
|
|
This adds a couple of configure commands to control whether we're
requiring all dependencies to be available locally (default) or not
(--enable-cargo-online-mode). When building from a tarball, we require
the RUST_DEPENDENCIES variable to point to the local repository of
crates. This also adds src/ext/rust as a git submodule that contains
such a local repository for easy setup.
|
|
Passing --enable-cargo-online-mode during configure allows cargo to make
network requests while building Tor or running tests. If this flag is
not supplied, the dependencies need to be available in the form of a
local mirror.
|
|
|