Incorrect configure scripts in Hackage-distributed packages?

[adamgundry]

Per configure.ac, the configure script is supposed to detect posix_spawn_file_actions_addchdir_np (cf #326). Indeed, running autoreconf -i in the git repo generates a configure script containing a section of "posix_spawn checks" that tests for posix_spawn_file_actions_addchdir_np. However the test for posix_spawn_file_actions_addchdir_np is missing from the distributed version from versions 1.6.19.0 through to 1.6.25.0 (e.g. see https://hackage.haskell.org/package/process-1.6.19.0/src/configure), and version 1.6.26.0 seems to be missing the "posix_spawn checks" entirely (https://hackage.haskell.org/package/process-1.6.26.0/src/configure). Perhaps a step was missed when uploading the source package to Hackage?

The result of this is that when I build locally from the git repo, configure detects posix_spawn_file_actions_addchdir_np correctly. However building the same package version in the Cabal store (as a dependency of another project) does not detect it.

(Related to #342.)

[bgamari]

Indeed I suspect that neither Tom nor I ran autoreconf prior to uploading. I will upload a new release.

[bgamari]

I have uploaded version 1.6.26.1.

[tomjaguarpaw]

The necessity of autoreconf is mentioned briefly in the README. Although cabal package uploaders might infer the necessity to run that command before cabal upload that does not seem to be documented anywhere and I simply didn't realise that I ought to do it. Let's make an issue about this and make it clearer for future uploaders.