Skip to content

building *-l4re-uclibc targets failed #165324

Closed

Description

@Wyvern

rustc 1.101.0-nightly (3e92e1a 2026-11-01)
building with -Zbuild-std
affected targets: aarch64-unknown-l4re-uclibc x86_64-unknown-l4re-uclibc

error[: cannot find module or crate `dir` in this scope
     ╭▸ /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/fs/unix.rs:1067:44
     │
1067 │                     mem::ManuallyDrop::new(dir::Dir(unsafe { OwnedFd::from_raw_fd(fd) }));
     │                                            ━━━ use of unresolved module or unlinked crate `dir`
     ╰╴
help: to make use of source file /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/sys/fs/unix/dir.rs, use `mod dir` in this file to declare the module
     ╭▸  /home/runner/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/std/src/lib.rs:454:1
     │
 454 + mod dir;
     ╰╴

For more information about this error, try `rustc --explain E0433`.
error: could not compile `std` (lib) due to 1 previous error

Activity

  1. added
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Nov 2, 2026
  2. maxdexh commented on Nov 2, 2026

    @maxdexh
    Member

    cc @farao (target maintainer)

  3. added
    T-libsRelevant to the library team, which will review and decide on the PR/issue.
    -Zbuild-stdUnstable cargo option: -Zbuild-std
    C-bugCategory: This is a bug.
    O-L4Rehttps://doc.rust-lang.org/beta/rustc/platform-support/l4re.html
    and removed
    needs-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
    on Nov 2, 2026
  4. Tushar15769 commented on Nov 2, 2026

    @Tushar15769
  5. workingjubilee commented on Nov 3, 2026

    @workingjubilee
    Member

    We don't do regression testing for tier 3 targets by definition of the target tier policy: https://doc.rust-lang.org/rustc/target-tier-policy.html#tier-3-target-policy

    Which is why we rely on individual reports and fixes, because they are not at a point where we can contemplate allowing them to block a merge, which tier 1 and tier 2 targets are allowed to do.

  6. Tushar15769 commented on Nov 3, 2026

    @Tushar15769
  7. Tushar15769 commented on Nov 3, 2026

    @Tushar15769
  8. farao commented on Nov 3, 2026

    @farao
    Contributor

    Hi! Thanks a lot for caring about the L4Re target! I'm happy to look into the issue later myself and also happy to be a reviewer of a change.

  9. farao commented on Nov 3, 2026

    @farao
    Contributor

    4. Could you please confirm if this is the intended approach to fix the issue, and whether you would be open to reviewing a contribution for it? Additionally, I'd appreciate any guidance you might have on setting up regression testing for this Tier 3 target.

    Agreed that this is the fix. Will you make a change or shall I?

  10. Tushar15769 commented on Nov 3, 2026

    @Tushar15769
  11. linked a pull request that will close this issuestd: Fix build for the L4Re targets #165456on Nov 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

-Zbuild-stdUnstable cargo option: -Zbuild-stdC-bugCategory: This is a bug.O-L4Rehttps://doc.rust-lang.org/beta/rustc/platform-support/l4re.htmlT-libsRelevant to the library team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions