Edit

kc3-lang/automake/m4/depend.m4

Branch :

  • Show log

    Commit

  • Author : Alexandre Duret-Lutz
    Date : 2004-04-12 16:59:09
    Hash : 61dbc304
    Message : Fix for PR automake/416: * m4/depend.m4 (_AM_DEPENDENCIES): Catch `not supported' ICC 8.0 remarks. From Peter Seiderer.

  • m4/depend.m4
  • # serial 7						-*- Autoconf -*-
    
    # Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004
    # Free Software Foundation, Inc.
    
    # This program is free software; you can redistribute it and/or modify
    # it under the terms of the GNU General Public License as published by
    # the Free Software Foundation; either version 2, or (at your option)
    # any later version.
    
    # This program is distributed in the hope that it will be useful,
    # but WITHOUT ANY WARRANTY; without even the implied warranty of
    # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
    # GNU General Public License for more details.
    
    # You should have received a copy of the GNU General Public License
    # along with this program; if not, write to the Free Software
    # Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
    # 02111-1307, USA.
    
    
    # There are a few dirty hacks below to avoid letting `AC_PROG_CC' be
    # written in clear, in which case automake, when reading aclocal.m4,
    # will think it sees a *use*, and therefore will trigger all it's
    # C support machinery.  Also note that it means that autoscan, seeing
    # CC etc. in the Makefile, will ask for an AC_PROG_CC use...
    
    
    
    # _AM_DEPENDENCIES(NAME)
    # ----------------------
    # See how the compiler implements dependency checking.
    # NAME is "CC", "CXX", "GCJ", or "OBJC".
    # We try a few techniques and use that to set a single cache variable.
    #
    # We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was
    # modified to invoke _AM_DEPENDENCIES(CC); we would have a circular
    # dependency, and given that the user is not expected to run this macro,
    # just rely on AC_PROG_CC.
    AC_DEFUN([_AM_DEPENDENCIES],
    [AC_REQUIRE([AM_SET_DEPDIR])dnl
    AC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnl
    AC_REQUIRE([AM_MAKE_INCLUDE])dnl
    AC_REQUIRE([AM_DEP_TRACK])dnl
    
    ifelse([$1], CC,   [depcc="$CC"   am_compiler_list=],
           [$1], CXX,  [depcc="$CXX"  am_compiler_list=],
           [$1], OBJC, [depcc="$OBJC" am_compiler_list='gcc3 gcc'],
           [$1], GCJ,  [depcc="$GCJ"  am_compiler_list='gcc3 gcc'],
                       [depcc="$$1"   am_compiler_list=])
    
    AC_CACHE_CHECK([dependency style of $depcc],
                   [am_cv_$1_dependencies_compiler_type],
    [if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then
      # We make a subdir and do the tests there.  Otherwise we can end up
      # making bogus files that we don't know about and never remove.  For
      # instance it was reported that on HP-UX the gcc test will end up
      # making a dummy file named `D' -- because `-MD' means `put the output
      # in D'.
      mkdir conftest.dir
      # Copy depcomp to subdir because otherwise we won't find it if we're
      # using a relative directory.
      cp "$am_depcomp" conftest.dir
      cd conftest.dir
      # We will build objects and dependencies in a subdirectory because
      # it helps to detect inapplicable dependency modes.  For instance
      # both Tru64's cc and ICC support -MD to output dependencies as a
      # side effect of compilation, but ICC will put the dependencies in
      # the current directory while Tru64 will put them in the object
      # directory.
      mkdir sub
    
      am_cv_$1_dependencies_compiler_type=none
      if test "$am_compiler_list" = ""; then
         am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp`
      fi
      for depmode in $am_compiler_list; do
        # Setup a source with many dependencies, because some compilers
        # like to wrap large dependency lists on column 80 (with \), and
        # we should not choose a depcomp mode which is confused by this.
        #
        # We need to recreate these files for each test, as the compiler may
        # overwrite some of them when testing with obscure command lines.
        # This happens at least with the AIX C compiler.
        : > sub/conftest.c
        for i in 1 2 3 4 5 6; do
          echo '#include "conftst'$i'.h"' >> sub/conftest.c
          # Using `: > sub/conftst$i.h' creates only sub/conftst1.h with
          # Solaris 8's {/usr,}/bin/sh.
          touch sub/conftst$i.h
        done
        echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf
    
        case $depmode in
        nosideeffect)
          # after this tag, mechanisms are not by side-effect, so they'll
          # only be used when explicitly requested
          if test "x$enable_dependency_tracking" = xyes; then
    	continue
          else
    	break
          fi
          ;;
        none) break ;;
        esac
        # We check with `-c' and `-o' for the sake of the "dashmstdout"
        # mode.  It turns out that the SunPro C++ compiler does not properly
        # handle `-M -o', and we need to detect this.
        if depmode=$depmode \
           source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \
           depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \
           $SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \
             >/dev/null 2>conftest.err &&
           grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 &&
           grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 &&
           ${MAKE-make} -s -f confmf > /dev/null 2>&1; then
          # icc doesn't choke on unknown options, it will just issue warnings
          # or remarks (even with -Werror).  So we grep stderr for any message
          # that says an option was ignored or not supported.
          # When given -MP, icc 7.0 and 7.1 complain thusly:
          #   icc: Command line warning: ignoring option '-M'; no argument required
          # The diagnosis changed in icc 8.0:
          #   icc: Command line remark: option '-MP' not supported
          if (grep 'ignoring option' conftest.err ||
              grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else
            am_cv_$1_dependencies_compiler_type=$depmode
            break
          fi
        fi
      done
    
      cd ..
      rm -rf conftest.dir
    else
      am_cv_$1_dependencies_compiler_type=none
    fi
    ])
    AC_SUBST([$1DEPMODE], [depmode=$am_cv_$1_dependencies_compiler_type])
    AM_CONDITIONAL([am__fastdep$1], [
      test "x$enable_dependency_tracking" != xno \
      && test "$am_cv_$1_dependencies_compiler_type" = gcc3])
    ])
    
    
    # AM_SET_DEPDIR
    # -------------
    # Choose a directory name for dependency files.
    # This macro is AC_REQUIREd in _AM_DEPENDENCIES
    AC_DEFUN([AM_SET_DEPDIR],
    [AC_REQUIRE([AM_SET_LEADING_DOT])dnl
    AC_SUBST([DEPDIR], ["${am__leading_dot}deps"])dnl
    ])
    
    
    # AM_DEP_TRACK
    # ------------
    AC_DEFUN([AM_DEP_TRACK],
    [AC_ARG_ENABLE(dependency-tracking,
    [  --disable-dependency-tracking  speeds up one-time build
      --enable-dependency-tracking   do not reject slow dependency extractors])
    if test "x$enable_dependency_tracking" != xno; then
      am_depcomp="$ac_aux_dir/depcomp"
      AMDEPBACKSLASH='\'
    fi
    AM_CONDITIONAL([AMDEP], [test "x$enable_dependency_tracking" != xno])
    AC_SUBST([AMDEPBACKSLASH])
    ])