packages/libflac: don't hardcode altivec options in CPUCFLAGS

The '-maltivec' and '-mabi=altivec' options always
included in the CPUCPFLAGS variable, even if altivec
support is disabled. This causes build failure on
powerpc platforms without altivec support:

  bitmath.c:1:0: error: AltiVec and E500 instructions cannot coexist

Update the src/libFLAC/Makefile.am template to skip
altivec options if 'FLaC__USE_ALTIVEC' is not used.

Signed-off-by: Gabor Juhos <juhosg@openwrt.org>

git-svn-id: svn://svn.openwrt.org/openwrt/packages@39443 3c298f89-4303-0410-b956-a3cf2f4a3e73
package/ffmpeg: remove trailing whitespaces from the Makefile

Signed-off-by: Gabor Juhos <juhosg@openwrt.org>

git-svn-id: svn://svn.openwrt.org/openwrt/packages@39444 3c298f89-4303-0410-b956-a3cf2f4a3e73
packages/ffmpeg: disable altivec support

The altivec support in the ffmpeg package is enabled
by default which causes the following build error on
powerpc targets:

  You need a compiler that supports {} in AltiVec vector declarations.

  If you think configure made a mistake, make sure you are using the latest
  version from Git.  If the latest version fails, report the problem to the
  ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.freenode.net.
  Include the log file "config.log" produced by configure as this will
  help solving the problem.

Altivec is not supported by any of our powerpc targets, so
disable that by default.

Signed-off-by: Gabor Juhos <juhosg@openwrt.org>

git-svn-id: svn://svn.openwrt.org/openwrt/packages@39445 3c298f89-4303-0410-b956-a3cf2f4a3e73