To ease cross-compilation of bzip2 NixOS uses https://ftp.suse.com/pub/people/sbrabec/bzip2/for_downstream/bzip2-1.0.6.2-autoconfiscated.patch version of autoconf build system for bzip2. WDYT of merging it upstream in some form? Currently NixOS generates ./configure using autoconf and automake. NixOS would prefer using autoconf-based upstream bzip2 release tarball without a dependency on these development tools. Thanks!
See Eli's patch series: https://sourceware.org/pipermail/bzip2-devel/2022q2/000166.html.
In general my understanding is that autoconfiscation patch you linked was explicitly rejected several times due to the "Incompatible changes" section. My patch series solves this problem and a number of other problems. It should also still work fine with cross-compilation, just specify `./configure --host=<triplet>` and it will set up e.g. `$CC` correctly.
(In reply to Eli Schwartz from comment #2) > In general my understanding is that autoconfiscation patch you linked was > explicitly rejected several times due to the "Incompatible changes" section. > > My patch series solves this problem and a number of other problems. It > should also still work fine with cross-compilation, just specify > `./configure --host=<triplet>` and it will set up e.g. `$CC` correctly. One comment... To cross-compile, you should specify both --build and --host. --build is easy. config.guess gives that triplet: $ find /usr/share -name config.guess ... /usr/share/autoconf/build-aux/config.guess $ /usr/share/autoconf/build-aux/config.guess x86_64-pc-linux-gnu --host is the trickier one. There is no list of cross-compile triplets. Also see https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Hosts-and-Cross_002dCompilation.html .