Fix for max size text chunks in aiff files.

Stop size rolling over to size zero.
fix lsx_filelength() prototype mismatach.

Fixes compile issue on OS X 10.9/llvm
Remove deprecated options in tests.
ladspa: optionally perform latency compensation

Some LADSPA plugins report their latency using a output control
port named "latency".  We may capture the latency of the plugin
and from that port to compensate for latency the plugin introduced.

This feature exists in Ardour and appears enabled by default[1].
This is not enabled by default in sox as existing scripts for older
versions of sox may already compensate for latency.

I've verified the output with the following no-op commands using on
tap_limiter (0.7.2) and sndfile-cmp on the results using the
following script:

----------------------------- 8< ----------------------------
  set -e

  # a.flac is a 24-bit, stereo, 44.1kHz FLAC file
  sox -n -r 48000 -c2 -b24 a.flac synth 5 pluck

  # original 24-bit FLAC, convert to 32-bit float and back to 24-bit wav
  sox a.flac -tf32 -c2 -r48000 - | sox -tf32 -r48000 -c2 - -b24 a.wav

  # no-op operation for tap_limiter, LADSPA uses float internally so
  # we expect this to give the same output as the above sox-only pipeline
  sox a.flac b.wav ladspa -rl tap_limiter 0 0

  sndfile-cmp a.wav b.wav
----------------------------- 8< ----------------------------

[1] - Based on my (limited) understanding of the Ardour code.
      I have not tested with Ardour as I am not comfortable with GUIs.
Add reading support for RF64 WAV files.

Based on specs from http://tech.ebu.ch/docs/tech/tech3306-2009.pdf.

Patch written by Dave Lambley
Work around for libsndfile size bug on RF64
fix warning on 64-bit arch.
AIFF comments implementation now passes this test
slight simplification
minor change: use periodic window
New libsox example6: give explicit output attributes
prevent division by 0 when input signal is entirely non-negative, non-positive, or both
Fix warning about ignored cdecl.

Only need value on prototype; not the implementation.
Switch to gcc's -fstack-protector

_FORTIFY_SOURCE=2 compiles fail with error on newer gccs if
-O is not enabled.  Instead of risking optimization related issues,
switching to gcc -fstack-protect (since 4.1 or 2007) or
-fstack-protector-strong (since 4.9 or 2014).

Redhat/Fedora ships with -fstack-protector for all RPM's and
is switching to -fstack-protector-strong this year so should be
well tested.

cmake could stand to be improved and enable -fstack-protector-strong
for newer compilers.
Default to silent mode for automake

Prevents the compiler warnings from being lost in the noise.

Use 'make V=1' to get older verbose compile output.