pixz.1 file check breaks cross-compiling

[vapier]

if you try to cross-compile pixz, it fails because of the use of AC_CHECK_FILE. simple fix is to just delete that.

if you want to keep the rule for git, you could always add it to the Makefile.am. or utilize the existing "maintainer mode" that autotools provides.

$ tar xf tar xf pixz-1.0.6.tar.xz 
$ cd pixz-1.0.6
$ ./configure --build=x86_64-pc-linux-gnu --host=powerpc-unknown-linux-gnu                                                                               checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for powerpc-unknown-linux-gnu-strip... powerpc-unknown-linux-gnu-strip
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk                                                                                                                                                           checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for style of include used by make... GNU
checking for powerpc-unknown-linux-gnu-gcc... powerpc-unknown-linux-gnu-gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... yes
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether powerpc-unknown-linux-gnu-gcc accepts -g... yes
checking for powerpc-unknown-linux-gnu-gcc option to accept ISO C89... none needed
checking whether powerpc-unknown-linux-gnu-gcc understands -c and -o together... yes
checking dependency style of powerpc-unknown-linux-gnu-gcc... gcc3
checking for powerpc-unknown-linux-gnu-gcc option to accept ISO C99... -std=gnu99
checking for powerpc-unknown-linux-gnu-gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99
checking for src/pixz.1... configure: error: cannot check for file existence when cross compiling

[DCNick3]

Same as #75. There is a patch addressing this in debian bugtracker.