Skip to content

Tracking Issue for raw-dylib on ELF #135694

Open

Description

@Noratrieb

This is a tracking issue for raw-dylib on ELF (no RFC, extending RFC 2627)
The feature gate for the issue is #![feature(raw_dylib_elf)].

raw-dylib on ELF links against a generated stub shared object, allowing linking against libraries that are not present on the host system, for example for cross-compilation scenarios.

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

Unresolved Questions

  • How to deal with symbol versioning?

Implementation history

Activity

  1. added
    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC
    T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.
    on Jan 18, 2025
  2. added a commit that references this issue on Feb 3, 2025
  3. added a commit that references this issue on Feb 3, 2025
  4. added 8 commits that reference this issue on Feb 12, 2025
  5. added 3 commits that reference this issue on Feb 26, 2025
  6. 9 remaining items

  7. added 3 commits that reference this issue on Jul 24, 2025
  8. added a commit that references this issue on Jul 24, 2025
  9. jethrogb commented on Aug 25, 2025

    @jethrogb
  10. bjorn3 commented on Aug 25, 2025

    @bjorn3
    Member

    Assembly has no effect on the generated .so raw-dylib file. Setting the symbol type correctly should be an easy fix.

  11. jethrogb commented on Aug 25, 2025

    @jethrogb
  12. mati865 commented on Aug 25, 2025

    @mati865
    Member

    Can you open a new issue for it?
    Tracking issues are not a good place for the discussions.

  13. added
    A-linkageArea: linking into static, shared libraries and binaries
    F-raw_dylib`#![feature(raw_dylib)]`
    and removed
    F-raw_dylib`#![feature(raw_dylib)]`
    on Sep 6, 2025
  14. added a commit that references this issue on Oct 6, 2025
  15. added a commit that references this issue on Oct 6, 2025
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

    A-linkageArea: linking into static, shared libraries and binariesC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCF-raw_dylib`#![feature(raw_dylib)]`T-compilerRelevant to the compiler 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