Skip to content

Unable to build due to dependency issue #18

Open

Description

@theaddonn

tried to build the examples and with the only dep being nx I got the follow issue:

   Compiling linked_list_allocator v0.10.5
    Buildingerror[E0599]: no method named `dangling` found for struct `Layout` in the current scope
   --> C:\Users\lucy\.cargo\registry\src\index.crates.io-1949cf8c6b5b557f\linked_list_allocator-0.10.5\src\lib.rs:273:60
    |
273 |             return Ok(NonNull::slice_from_raw_parts(layout.dangling(), 0));
    |                                                            ^^^^^^^^
    |
help: there is a method `dangling_ptr` with a similar name
    |
273 |             return Ok(NonNull::slice_from_raw_parts(layout.dangling_ptr(), 0));
    |                                                                    ++++


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

Activity

  1. XorTroll commented on Mar 21, 2026

    @XorTroll
    Contributor

    Have you tried updating nightly Rust? I believe that fixed the issue on my end

  2. sermuns commented on Mar 21, 2026

    @sermuns

    dangling was renamed to dangling_ptr: rust-lang/rust#148769 (comment)

  3. sermuns commented on Mar 21, 2026

    @sermuns

    One shitty workaround is to pin to the nightly version before this was merged, e.g. creating rust-toolchain.toml with

    [toolchain]
    channel = "nightly-2026-01-18"
    components = ["rust-src"]

    But if I understand correctly, the real solution is for linked_list_allocator to change their code?

  4. sermuns commented on Mar 21, 2026

    @sermuns

    I have opened PR on linked_list_allocator: rust-osdev/linked-list-allocator#90

  5. pantsman0 commented on Mar 31, 2026

    @pantsman0
    Member

    @XorTroll There doesn't seem to be much urgency on the LL allocator side - we could consider a similar allocator such as buddy_system_allocator?

  6. XorTroll commented on Apr 2, 2026

    @XorTroll
    Contributor

    Yeah absolutely, I'd rather rely on a somewhat maintained allocator to avoid these dependency issues in the future

  7. sermuns commented on Apr 2, 2026

    @sermuns

    @XorTroll @pantsman0 I am very interested in contributing to the aarch64-switch-rs org,
    I could for example compare allocator crates, then make a PR, depending on what you think.

    Do you have some sort of direct channel or should we continue communication in this thread?

  8. pantsman0 commented on Apr 2, 2026

    @pantsman0
    Member

    aarch64-switch-rs/nx#60 @sermuns

    Feel free to put some options in there and we can make a decision from there

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions