Skip to content

[SR-10625] tests for -static-* #53025

@weissi

Description

@weissi
Previous ID SR-10625
Radar rdar://problem/52529025
Original Reporter @weissi
Type Bug
Additional Detail from JIRA
Votes 0
Component/s Compiler, Project Infrastructure, Standard Library
Labels Bug, Test
Assignee None
Priority Medium

md5: 6f1a41499babf8d8e6c8bbe317eda225

relates to:

  • SR-648 swift package manager should have the option to produce statically linked binaries
  • SR-2205 Linker fails when linking to Foundation if -static-stdlib flag is present
  • SR-4974 Cannot build Android static lib on macOS
  • SR-6481 Statically linked stdlib fails for cross-compilation from OSX to Ubuntu
  • SR-6858 Swift Static-Stdlib on Windows doesn't build correctly
  • SR-9368 libdispatch_static unit tests are disabled
  • SR-9384 Figure out why Foundation integration test for compiling on Linux with -static-stdlib fails
  • SR-7039 can't use -static-stdlib (or -static-executable) with any Dispatch using app
  • SR-10623 static-executable fully broken now
  • SR-10624 SwiftPM doesn't hand --swift-static-stdlib through

Issue Description:

Swift doesn't seem to have any (integration?) tests for the static-* parameters. They get broken all the time. We should clearly know what works and what doesn't. As of 5.0 I think pretty much everything is broken on Linux (static-executable works nowhere, static-stdlib doesn't work when Dispatch is involved.)

For example:

On top of the compiler, SwiftPM has bugs in that area too, for example https://bugs.swift.org/browse/SR-10624

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugA deviation from expected or documented behavior. Also: expected but undesirable behavior.compilerThe Swift compiler itselfstandard libraryArea: Standard library umbrella

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions