Fixed Bugs When Not Using Default Target Directory

[zcg00]

• Changes stdbuf's build script to allow target directory to not require 'target' or 'cargo-install' in name
• Updates scripts to use "CARGO_TARGET_DIR" when supplied

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)
Skipping an intermittent issue tests/misc/stdbuf (passes in this run but fails in the 'main' branch)
Skipping an intermittent issue tests/misc/usage_vs_getopt (passes in this run but fails in the 'main' branch)

[sylvestre]

some jobs are failing, could you please have a look?

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/timeout/timeout (passes in this run but fails in the 'main' branch)

[RenjiSann]

Other than my remark on the fixup commit, it looks OK to me 👍

[RenjiSann]

There are fails in the CI, I will try to look at them tomorrow if no one does before me.

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/timeout/timeout (fails in this run but passes in the 'main' branch)

[RenjiSann]

It looks like the install method using cross does not work. I'm not familiar with this, so I might take some time before I understand what the problem is.

As a reminder, there was actually a warning in build.rs that said it should be tested with cross.

[RenjiSann]

It looks like the install method using cross does not work. I'm not familiar with this, so I might take some time before I understand what the problem is.

As a reminder, there was actually a warning in build.rs that said it should be tested with cross.

OK so I don't know if this is expected behavior from cross or not, and to what extent this is tight to my dev setup, but when I run this:

cross +1.79.0 build --release --target=x86_64-unknown-linux-gnu

The OUT_DIR given to the build.rs script is target/x86_64-unknown-linux-gnu/release/deps/.

For some reason, liblibstdbuf.so still gets created in target/release/deps, so that's why the .find() call fails.

[github-actions]

GNU testsuite comparison:

Skip an intermittent issue tests/misc/stdbuf (fails in this run but passes in the 'main' branch)

[RenjiSann]

LGTM 👍 but as I'm not an expert in this domain, I'll let someone cross check before merging.
Maybe @sylvestre ?

[github-actions]

GNU testsuite comparison:

GNU test failed: tests/test/test. tests/test/test is passing on 'main'. Maybe you have to rebase?
Skipping an intermittent issue tests/timeout/timeout (passes in this run but fails in the 'main' branch)

[github-actions]

GNU testsuite comparison:

Skipping an intermittent issue tests/timeout/timeout (passes in this run but fails in the 'main' branch)

[Copilot]

PR Overview

This PR fixes the process of locating the dependencies directory during the build, allowing the target directory to have a flexible name (i.e. not requiring "target" or "cargo-install").

• Replaces the iterative parent lookup from OUT_DIR with a lookup based on the executable's ancestry.
• Updates the file copy logic to reflect the new directory resolution.

Reviewed Changes

File	Description
src/uu/stdbuf/build.rs	Revised logic for determining the deps directory using current_exe and ancestors

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

Comments suppressed due to low confidence (1)

src/uu/stdbuf/build.rs:33

• Using nth(3) from current_exe ancestors may be brittle if the executable path structure changes; consider adding error handling or a more robust method to determine the dependencies directory.

let deps_dir = current_exe.ancestors().nth(3).unwrap().join("deps");