Build failure: vmware-horizon-client

[TheSirC]

Steps To Reproduce

Steps to reproduce the behavior:

1. build vmware-horizon-client with env NIXPKGS_ALLOW_UNFREE=1 nix shell --impure github:NixOS/nixpkgs#vmware-horizon-client
2. Notice build failure

Build log

@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/4l23b1hn92ihijylsc9hr0vyfwiq8xcs-src
source root is src
@nix { "action": "setPhase", "phase": "patchPhase" }
patching sources
@nix { "action": "setPhase", "phase": "updateAutotoolsGnuConfigScriptsPhase" }
updateAutotoolsGnuConfigScriptsPhase
@nix { "action": "setPhase", "phase": "configurePhase" }
configuring
meson flags: --buildtype=plain         --libdir=/nix/store/jnz3cf3pq7qcgjqfxvscilyjc6wzqhks-chrootenv/lib --libexecdir=/nix/store/jnz3cf3pq7qcgjqfxvscilyjc6wzqhks-chrootenv/libexec         --bindir=/nix/store/jnz>
The Meson build system
Version: 1.1.1
Source dir: /build/src
Build dir: /build/src/build
Build type: native build
Project name: chrootenv
Project version: undefined

meson.build:1:0: ERROR: Executables created by c compiler gcc are not runnable.

Additional context

Tested with 100a1550b0e7a64b960c625b656f9229bdef5f87

Notify maintainers

@buckley310

Metadata

Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.27, NixOS, 23.05 (Stoat), 23.05pre-git`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.15.0`
 - channels(root): `""`
 - nixpkgs: `/nix/store/ry2fd2lgrqkqmxdx9xzqp7ix1xnrav10-nixos-unstable-2023-05-06`

[buckley310]

That command appears to be running the app directly from the master branch.

The following works for me, try this:

env NIXPKGS_ALLOW_UNFREE=1 nix run --impure github:NixOS/nixpkgs/nixos-unstable#vmware-horizon-client

[TheSirC]

This command still sends back the the same error log as the one stated in the original post

[buckley310]

Is your root filesystem or /tmp mounted with noexec? https://github.com/NixOS/nixpkgs/issues/115018

[TheSirC]

No.

[buckley310]

What happens if you run this?

NIXPKGS_ALLOW_UNFREE=1 nix build -L --impure nixpkgs/nixos-unstable#hello-unfree

[TheSirC]

Package built fine without hiccups :

example-unfree-package> patching sources
example-unfree-package> updateAutotoolsGnuConfigScriptsPhase
example-unfree-package> configuring
example-unfree-package> no configure script, doing nothing
example-unfree-package> building
example-unfree-package> no Makefile or custom buildPhase, doing nothing
example-unfree-package> installing
example-unfree-package> post-installation fixup
example-unfree-package> shrinking RPATHs of ELF executables and libraries in /nix/store/fpvihxhzqvzni9mkgbkwh0hxz1wnha6i-example-unfree-package-1.0
example-unfree-package> checking for references to /build/ in /nix/store/fpvihxhzqvzni9mkgbkwh0hxz1wnha6i-example-unfree-package-1.0...
example-unfree-package> patching script interpreter paths in /nix/store/fpvihxhzqvzni9mkgbkwh0hxz1wnha6i-example-unfree-package-1.0
example-unfree-package> stripping (with command strip and flags -S -p) in  /nix/store/fpvihxhzqvzni9mkgbkwh0hxz1wnha6i-example-unfree-package-1.0/bin

[buckley310]

I'm not really sure what to try next. Are you able to produce an example nixos config I can run in a VM that recreates the issue?

[TheSirC]

I will try to bisect the commit that introduced the failure. I am pining nixpkgs to this commit (https://github.com/NixOS/nixpkgs/commit/100a1550b0e7a64b960c625b656f9229bdef5f8) so I imagine that it should not be too difficult (famous last words)