-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
Open
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: architectureRelating to code and API architecture of NixpkgsRelating to code and API architecture of Nixpkgs6.topic: cross-compilationBuilding packages on a different platform than they will be used onBuilding packages on a different platform than they will be used on6.topic: muslRunning or building packages with musl libcRunning or building packages with musl libc6.topic: staticStatic builds (e.g. pkgsStatic)Static builds (e.g. pkgsStatic)
Description
Issue description
For my work on static-haskell-nix I need an overlay that has both .so files and .a files.
This is because I need .as for linking Haskell exes statically, but .so files for executing TemplateHaskell.
Right now pkgsStatic not only adds .a files, but also disables .so files:
makeStaticBinariesandmakeStaticLibrariesset--disable-sharedstatic.nixuses thosestatic.nixdisables shared Haskell libs that TH needs
Proposal
I think we should have the following stack of overlays:
pkgsMusl <- pkgsStatic <- pkgsStaticOnly
pkgsMuslis what it is now: All packages using musl libcpkgsStaticshould be the one that has.afiles added to all libraries (in addition to.sofiles), and all binaries (including Haskell ones) linked statically where possiblepkgsStaticOnlyshould be whatpkgsStaticis now: Having only static libraries and binaries, getting rid of.sofiles.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.mdhttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: architectureRelating to code and API architecture of NixpkgsRelating to code and API architecture of Nixpkgs6.topic: cross-compilationBuilding packages on a different platform than they will be used onBuilding packages on a different platform than they will be used on6.topic: muslRunning or building packages with musl libcRunning or building packages with musl libc6.topic: staticStatic builds (e.g. pkgsStatic)Static builds (e.g. pkgsStatic)