sooperlooper compat 10
jcowgill at debian.org
Sat Jan 7 19:08:16 UTC 2017
On 07/01/17 14:33, Jaromír Mikeš wrote:
> 2016-12-17 22:57 GMT+01:00 Jaromír Mikeš <mira.mikes at gmail.com>:
>> 2016-12-17 22:56 GMT+01:00 Jaromír Mikeš <mira.mikes at gmail.com>:
>>> sooperlooper build fine with dh 10 but fail with compat 10 ...
>>> What I am missing?
>> here is build log
>> configure.ac:51: warning: macro 'AM_OPT_FLAGS' not found in library
>> configure.ac:367: warning: macro 'AM_BUILD_ENVIRONMENT' not found in library
>> configure.ac:35: warning: macro 'AM_OPT_FLAGS' not found in library
>> configure.ac:207: warning: macro 'AM_BUILD_ENVIRONMENT' not found in library
>> configure.ac:35: error: possibly undefined macro: AM_OPT_FLAGS
>> If this token and others are legitimate, please use m4_pattern_allow.
>> See the Autoconf documentation.
>> configure.ac:207: error: possibly undefined macro: AM_BUILD_ENVIRONMENT
>> autoreconf: /usr/bin/autoconf failed with exit status: 1
>> dh_autoreconf: autoreconf -f -i returned exit code 1
>> debian/rules:15: recipe for target 'build' failed
>> make: *** [build] Error 2
> ping ;)
> sooperlooper build with compat 9 but not with compat 10 ...
Compat 10 enabled autoreconf by default, but unfortunately these macros
are added to aclocal manually by autogen.sh which autoreconf ignores.
The "correct" thing to do would be to put the macros in the m4 directory
(it always annoys me when upstreams put lots of pointless stuff in
For the package you can probably get away with disabling autoreconf and
running autogen.sh manually.
I also notice AM_OPT_FLAGS macro contains some funky per-cpu
optimization flags (configured depending on build cpu) which I would
patch out (the bit from 'if test "\$target_cpu" = "powerpc"; then' to
it's corresponding 'fi').
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 833 bytes
Desc: OpenPGP digital signature
More information about the pkg-multimedia-maintainers