On 07/01/2014 10:09 AM, Bill Allombert wrote:
Is it possible to pass  -Wno-obsolete as an argument to automake instead of
patching configure.ac ?

It seems not to be possible. Even with -Wno-obsolete (or its variant)
specified, automake fails with that error.


        $ autoreconf -fvi -Wno-obsolete
        [...]
autoreconf: running: automake-1.11 --add-missing --copy --force-missing *--warnings=no-obsolete*
        [...]
        configure.ac:24: automatic de-ANSI-fication support is deprecated
        autoreconf: automake-1.11 failed with exit status: 1
        $


        $ automake-1.11 *-Wno-obsolete*
        [...]
        configure.ac:24: automatic de-ANSI-fication support is deprecated
        $


I believe the value is re-set when parsing AM_INIT_AUTOMAKE. I looked in
some of automake's perl modules, but couldn't find its right spot.

from Automake/Options.pm:

"""
This packages manages Automake's options and strictness settings.
Options can be either local or global.  Local options are set using an
C<AUTOMAKE_OPTIONS> variable in a F<Makefile.am> and apply only to
this F<Makefile.am>.  Global options are set from the command line or
passed as an argument to C<AM_INIT_AUTOMAKE>, they apply to all
F<Makefile.am>s.
"""

So maybe local options override global options.


Clearly, the original files were generated without patching.

Agreed. I would think it might have happened when ansi2knr was not
yet deprecated, or a local option was used in a Makefile.am, maybe
both.. maybe none. :)



If I got you right, the inconvenience itself seems to be carrying
a patch only for that matter, if an env var/cmdline arg could do.
So, for that, I wouldn't know another option.

On the side of causing no difference compared without -Wno-obsolete,
I can confirm the packages generated in ppc64el (with that patch)
and powerpc are identical in terms of files -- so the patch/option
doesn't affect the expected build output:


        $ for dir in ppc64el/ powerpc/; do
          cd $dir &&
          mkdir contents &&
        
          for deb in *.deb; do
            dpkg-deb -c $deb
              | cut -d. -f2-
              | sort
              | sed 's,\(powerpc64le\|powerpc\),GNU_ARCH,g'
              > contents/${deb%%_*};
            done &&
            cd .. ;
        
          done

        $ diff -r ppc64el/contents/ powerpc/contents/
        $ echo $?
        0


Would that be OK with the rationale above?

Thank you,

--
Mauricio Faria de Oliveira
IBM Linux Technology Center


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to