Tracking Issue for raw-dylib on ELF

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

• Initial implementation (#135695)
• Wider Testing
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• How to deal with symbol versioning?

Implementation history

• Initial implementation: #135695
• Symbol versioning support: #144221
• as-needed modifier support: #146027
• correct symbol type for functions: #153090
• fix statics support: #153580

Start with RFC 2627 and the implementation history, especially PRs #135695, #144221, #146027, #153090, and #153580. Review the remaining checklist and the unresolved symbol-versioning question, then consult the stabilization and documentation guides. Done requires wider testing, documentation updates, resolution of open design questions, and a stabilization PR.