btrfs-progs fails to cross-compile

I can build it natively on aarch64 or x86_64. Only cross-compilation fails

To reproduce, run (on x86_64 host)

guix build btrfs-progs --target=aarch64-linux-gnu

Output:

configure: error: Package requirements (libudev) were not met:

No package 'libudev' found

Consider adjusting the PKG_CONFIG_PATH environment variable if you

installed software in a non-standard prefix.

Alternatively, you may set the environment variables LIBUDEV_CFLAGS

and LIBUDEV_LIBS to avoid the need to call pkg-config.

See the pkg-config man page for more details.

error: in phase 'configure': uncaught exception:

%exception #<&invoke-error program: "/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" arguments: ("./configure" "CC_FOR_BUILD=gcc" "CONFIG_SHELL=/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" "SHELL=/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" "--prefix=/gnu/store/0sa8vdwlg49bdcshpnp8ry0mjszncn40-btrfs-progs-5.15.1" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--host=aarch64-linux-gnu") exit-status: 1 term-signal: #f stop-signal: #f>

phase `configure' failed after 1.1 seconds

command "/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" "./configure" "CC_FOR_BUILD=gcc" "CONFIG_SHELL=/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" "SHELL=/gnu/store/4y5m9lb8k3qkb1y9m02sw9w9a6hacd16-bash-minimal-5.1.8/bin/bash" "--prefix=/gnu/store/0sa8vdwlg49bdcshpnp8ry0mjszncn40-btrfs-progs-5.15.1" "--enable-fast-install" "--build=x86_64-unknown-linux-gnu" "--host=aarch64-linux-gnu" failed with status 1

Pavel Shlyak schreef op za 21-05-2022 om 21:02 [+0300]:

Given that 'eudev' appears in the references, it looks like 'eudev'

needs to be moved from native-inputs to inputs (apparently it's not

only for tests!) in the package definition of btrfs-progs.

Greetings,

Maxime.

Pavel,

Pavel Shlyak ???

Thanks. This was due to

- a bogus eudev native-input that should have been regular,

- broken Python support somewhere upstream.

Handily, said Python support was never actually used by Guix, so

we can just ignore it and --disable-python.

Kind regards,

T G-R