Skip to content

CI for static builds #144207

Closed
Closed
CI for static builds#144207
Labels
0.kind: bugSomething is broken2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: continuous integrationAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions6.topic: staticStatic builds (e.g. pkgsStatic)
@KAction

Description

@KAction
KAction
opened on Nov 2, 2021

I fixed static build of opens in [4879ea9], but as of [31b4955] it is broken again:

...
/nix/store/syy77y0g93whfm2q7vawcgcjby41kwcm-x86_64-unknown-linux-musl-binutils-2.35.1/bin/x86_64-unknown-linux-musl-ld: /nix/store/82y864wrlmlqkw3mmydpkwp20gv0mnqa-libkrb5-1.18-x86_64-u
nknown-linux-musl/lib/libkrb5.a(cc_keyring.o): in function `krcc_generate_new':
/nix/store/syy77y0g93whfm2q7vawcgcjby41kwcm-x86_64-unknown-linux-musl-binutils-2.35.1/bin/x86_64-unknown-linux-musl-ld: /nix/store/82y864wrlmlqkw3mmydpkwp20gv0mnqa-libkrb5-1.18-x86_64-u
nknown-linux-musl/lib/libkrb5.a(cc_keyring.o): in function `krcc_generate_new':
(.text+0x1f00): undefined reference to `keyctl_search'
(.text+0x1f00): undefined reference to `keyctl_search'
/nix/store/syy77y0g93whfm2q7vawcgcjby41kwcm-x86_64-unknown-linux-musl-binutils-2.35.1/bin/x86_64-unknown-linux-musl-ld: (.text+0x1f8a): undefined reference to `add_key'
/nix/store/syy77y0g93whfm2q7vawcgcjby41kwcm-x86_64-unknown-linux-musl-binutils-2.35.1/bin/x86_64-unknown-linux-musl-ld: (.text+0x1f8a): undefined reference to `add_key'
collect2: error: ld returned 1 exit status
collect2: error: ld returned 1 exit status
make: *** [Makefile:210: ssh] Error 1
make: *** [Makefile:210: ssh] Error 1
builder for '/nix/store/mwnjzygh8mzw5ils01prfkirbfn8wq16-openssh-static-x86_64-unknown-linux-musl-8.7p1.drv' failed with exit code 2

There was quite a refactoring of openssh, according to git-blame, and I am still bisecting it. I'll probably fix it in weeks coming, but real question is to how to make fixed stuff fixed.

As I understand, static builds are not really checked by Hydra, in particular because unknown subset of them actually works.

So here I come with proposal -- export packages that are known to build statically as "static-foo" (subject to bike shedding)
in top-level/all-packages.nix, so we keep track of what is supposed to work and can check whether any particular patch broke it.

Opinions? Better proposals?

Metadata

Metadata

Assignees

No one assigned

    Labels

    0.kind: bugSomething is broken2.status: stalehttps://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md6.topic: continuous integrationAffects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions6.topic: staticStatic builds (e.g. pkgsStatic)

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions