Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

Use AM_INIT_AUTOMAKE to install config.guess and config.sub.

git-svn-id: https://xbmc.svn.sourceforge.net/svnroot/xbmc/trunk@28862 568bbfeb-2a22-0410-94d2-cc84cf5bfa90
  • Loading branch information...
commit 2cc3456d8e1c6158fae4286d25929945b7ec1fea 1 parent f42cec2
ceros7 authored
2  .dummy.am
... ... @@ -0,0 +1,2 @@
  1 +# Does nothing intentionally.
  2 +# This exists solely so we can use AM_INIT_AUTOMAKE in configure.in
1  .gitignore
@@ -45,6 +45,7 @@ config.log
45 45 /xbmc-xrandr
46 46 /svn_revision.h
47 47 /build
  48 +/.dummy.in
48 49
49 50 # /guilib/
50 51 /guilib/Makefile
2  AUTHORS
... ... @@ -0,0 +1,2 @@
  1 +See 'tools/Linux/packaging/debian/copyright' for all author and credits
  2 +information.
1  COPYING
... ... @@ -0,0 +1 @@
  1 +See LICENSE.GPL.
3  ChangeLog
... ... @@ -0,0 +1,3 @@
  1 +Please use 'git log' or 'svn log' for changelog information. You may also use
  2 +http://xbmc.git.sourceforge.net/git/gitweb.cgi?p=xbmc/xbmc;a=shortlog to view
  3 +changes to SVN trunk.
365 INSTALL
... ... @@ -0,0 +1,365 @@
  1 +Installation Instructions
  2 +*************************
  3 +
  4 +Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005,
  5 +2006, 2007, 2008, 2009 Free Software Foundation, Inc.
  6 +
  7 + Copying and distribution of this file, with or without modification,
  8 +are permitted in any medium without royalty provided the copyright
  9 +notice and this notice are preserved. This file is offered as-is,
  10 +without warranty of any kind.
  11 +
  12 +Basic Installation
  13 +==================
  14 +
  15 + Briefly, the shell commands `./configure; make; make install' should
  16 +configure, build, and install this package. The following
  17 +more-detailed instructions are generic; see the `README' file for
  18 +instructions specific to this package. Some packages provide this
  19 +`INSTALL' file but do not implement all of the features documented
  20 +below. The lack of an optional feature in a given package is not
  21 +necessarily a bug. More recommendations for GNU packages can be found
  22 +in *note Makefile Conventions: (standards)Makefile Conventions.
  23 +
  24 + The `configure' shell script attempts to guess correct values for
  25 +various system-dependent variables used during compilation. It uses
  26 +those values to create a `Makefile' in each directory of the package.
  27 +It may also create one or more `.h' files containing system-dependent
  28 +definitions. Finally, it creates a shell script `config.status' that
  29 +you can run in the future to recreate the current configuration, and a
  30 +file `config.log' containing compiler output (useful mainly for
  31 +debugging `configure').
  32 +
  33 + It can also use an optional file (typically called `config.cache'
  34 +and enabled with `--cache-file=config.cache' or simply `-C') that saves
  35 +the results of its tests to speed up reconfiguring. Caching is
  36 +disabled by default to prevent problems with accidental use of stale
  37 +cache files.
  38 +
  39 + If you need to do unusual things to compile the package, please try
  40 +to figure out how `configure' could check whether to do them, and mail
  41 +diffs or instructions to the address given in the `README' so they can
  42 +be considered for the next release. If you are using the cache, and at
  43 +some point `config.cache' contains results you don't want to keep, you
  44 +may remove or edit it.
  45 +
  46 + The file `configure.ac' (or `configure.in') is used to create
  47 +`configure' by a program called `autoconf'. You need `configure.ac' if
  48 +you want to change it or regenerate `configure' using a newer version
  49 +of `autoconf'.
  50 +
  51 + The simplest way to compile this package is:
  52 +
  53 + 1. `cd' to the directory containing the package's source code and type
  54 + `./configure' to configure the package for your system.
  55 +
  56 + Running `configure' might take a while. While running, it prints
  57 + some messages telling which features it is checking for.
  58 +
  59 + 2. Type `make' to compile the package.
  60 +
  61 + 3. Optionally, type `make check' to run any self-tests that come with
  62 + the package, generally using the just-built uninstalled binaries.
  63 +
  64 + 4. Type `make install' to install the programs and any data files and
  65 + documentation. When installing into a prefix owned by root, it is
  66 + recommended that the package be configured and built as a regular
  67 + user, and only the `make install' phase executed with root
  68 + privileges.
  69 +
  70 + 5. Optionally, type `make installcheck' to repeat any self-tests, but
  71 + this time using the binaries in their final installed location.
  72 + This target does not install anything. Running this target as a
  73 + regular user, particularly if the prior `make install' required
  74 + root privileges, verifies that the installation completed
  75 + correctly.
  76 +
  77 + 6. You can remove the program binaries and object files from the
  78 + source code directory by typing `make clean'. To also remove the
  79 + files that `configure' created (so you can compile the package for
  80 + a different kind of computer), type `make distclean'. There is
  81 + also a `make maintainer-clean' target, but that is intended mainly
  82 + for the package's developers. If you use it, you may have to get
  83 + all sorts of other programs in order to regenerate files that came
  84 + with the distribution.
  85 +
  86 + 7. Often, you can also type `make uninstall' to remove the installed
  87 + files again. In practice, not all packages have tested that
  88 + uninstallation works correctly, even though it is required by the
  89 + GNU Coding Standards.
  90 +
  91 + 8. Some packages, particularly those that use Automake, provide `make
  92 + distcheck', which can by used by developers to test that all other
  93 + targets like `make install' and `make uninstall' work correctly.
  94 + This target is generally not run by end users.
  95 +
  96 +Compilers and Options
  97 +=====================
  98 +
  99 + Some systems require unusual options for compilation or linking that
  100 +the `configure' script does not know about. Run `./configure --help'
  101 +for details on some of the pertinent environment variables.
  102 +
  103 + You can give `configure' initial values for configuration parameters
  104 +by setting variables in the command line or in the environment. Here
  105 +is an example:
  106 +
  107 + ./configure CC=c99 CFLAGS=-g LIBS=-lposix
  108 +
  109 + *Note Defining Variables::, for more details.
  110 +
  111 +Compiling For Multiple Architectures
  112 +====================================
  113 +
  114 + You can compile the package for more than one kind of computer at the
  115 +same time, by placing the object files for each architecture in their
  116 +own directory. To do this, you can use GNU `make'. `cd' to the
  117 +directory where you want the object files and executables to go and run
  118 +the `configure' script. `configure' automatically checks for the
  119 +source code in the directory that `configure' is in and in `..'. This
  120 +is known as a "VPATH" build.
  121 +
  122 + With a non-GNU `make', it is safer to compile the package for one
  123 +architecture at a time in the source code directory. After you have
  124 +installed the package for one architecture, use `make distclean' before
  125 +reconfiguring for another architecture.
  126 +
  127 + On MacOS X 10.5 and later systems, you can create libraries and
  128 +executables that work on multiple system types--known as "fat" or
  129 +"universal" binaries--by specifying multiple `-arch' options to the
  130 +compiler but only a single `-arch' option to the preprocessor. Like
  131 +this:
  132 +
  133 + ./configure CC="gcc -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
  134 + CXX="g++ -arch i386 -arch x86_64 -arch ppc -arch ppc64" \
  135 + CPP="gcc -E" CXXCPP="g++ -E"
  136 +
  137 + This is not guaranteed to produce working output in all cases, you
  138 +may have to build one architecture at a time and combine the results
  139 +using the `lipo' tool if you have problems.
  140 +
  141 +Installation Names
  142 +==================
  143 +
  144 + By default, `make install' installs the package's commands under
  145 +`/usr/local/bin', include files under `/usr/local/include', etc. You
  146 +can specify an installation prefix other than `/usr/local' by giving
  147 +`configure' the option `--prefix=PREFIX', where PREFIX must be an
  148 +absolute file name.
  149 +
  150 + You can specify separate installation prefixes for
  151 +architecture-specific files and architecture-independent files. If you
  152 +pass the option `--exec-prefix=PREFIX' to `configure', the package uses
  153 +PREFIX as the prefix for installing programs and libraries.
  154 +Documentation and other data files still use the regular prefix.
  155 +
  156 + In addition, if you use an unusual directory layout you can give
  157 +options like `--bindir=DIR' to specify different values for particular
  158 +kinds of files. Run `configure --help' for a list of the directories
  159 +you can set and what kinds of files go in them. In general, the
  160 +default for these options is expressed in terms of `${prefix}', so that
  161 +specifying just `--prefix' will affect all of the other directory
  162 +specifications that were not explicitly provided.
  163 +
  164 + The most portable way to affect installation locations is to pass the
  165 +correct locations to `configure'; however, many packages provide one or
  166 +both of the following shortcuts of passing variable assignments to the
  167 +`make install' command line to change installation locations without
  168 +having to reconfigure or recompile.
  169 +
  170 + The first method involves providing an override variable for each
  171 +affected directory. For example, `make install
  172 +prefix=/alternate/directory' will choose an alternate location for all
  173 +directory configuration variables that were expressed in terms of
  174 +`${prefix}'. Any directories that were specified during `configure',
  175 +but not in terms of `${prefix}', must each be overridden at install
  176 +time for the entire installation to be relocated. The approach of
  177 +makefile variable overrides for each directory variable is required by
  178 +the GNU Coding Standards, and ideally causes no recompilation.
  179 +However, some platforms have known limitations with the semantics of
  180 +shared libraries that end up requiring recompilation when using this
  181 +method, particularly noticeable in packages that use GNU Libtool.
  182 +
  183 + The second method involves providing the `DESTDIR' variable. For
  184 +example, `make install DESTDIR=/alternate/directory' will prepend
  185 +`/alternate/directory' before all installation names. The approach of
  186 +`DESTDIR' overrides is not required by the GNU Coding Standards, and
  187 +does not work on platforms that have drive letters. On the other hand,
  188 +it does better at avoiding recompilation issues, and works well even
  189 +when some directory options were not specified in terms of `${prefix}'
  190 +at `configure' time.
  191 +
  192 +Optional Features
  193 +=================
  194 +
  195 + If the package supports it, you can cause programs to be installed
  196 +with an extra prefix or suffix on their names by giving `configure' the
  197 +option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
  198 +
  199 + Some packages pay attention to `--enable-FEATURE' options to
  200 +`configure', where FEATURE indicates an optional part of the package.
  201 +They may also pay attention to `--with-PACKAGE' options, where PACKAGE
  202 +is something like `gnu-as' or `x' (for the X Window System). The
  203 +`README' should mention any `--enable-' and `--with-' options that the
  204 +package recognizes.
  205 +
  206 + For packages that use the X Window System, `configure' can usually
  207 +find the X include and library files automatically, but if it doesn't,
  208 +you can use the `configure' options `--x-includes=DIR' and
  209 +`--x-libraries=DIR' to specify their locations.
  210 +
  211 + Some packages offer the ability to configure how verbose the
  212 +execution of `make' will be. For these packages, running `./configure
  213 +--enable-silent-rules' sets the default to minimal output, which can be
  214 +overridden with `make V=1'; while running `./configure
  215 +--disable-silent-rules' sets the default to verbose, which can be
  216 +overridden with `make V=0'.
  217 +
  218 +Particular systems
  219 +==================
  220 +
  221 + On HP-UX, the default C compiler is not ANSI C compatible. If GNU
  222 +CC is not installed, it is recommended to use the following options in
  223 +order to use an ANSI C compiler:
  224 +
  225 + ./configure CC="cc -Ae -D_XOPEN_SOURCE=500"
  226 +
  227 +and if that doesn't work, install pre-built binaries of GCC for HP-UX.
  228 +
  229 + On OSF/1 a.k.a. Tru64, some versions of the default C compiler cannot
  230 +parse its `<wchar.h>' header file. The option `-nodtk' can be used as
  231 +a workaround. If GNU CC is not installed, it is therefore recommended
  232 +to try
  233 +
  234 + ./configure CC="cc"
  235 +
  236 +and if that doesn't work, try
  237 +
  238 + ./configure CC="cc -nodtk"
  239 +
  240 + On Solaris, don't put `/usr/ucb' early in your `PATH'. This
  241 +directory contains several dysfunctional programs; working variants of
  242 +these programs are available in `/usr/bin'. So, if you need `/usr/ucb'
  243 +in your `PATH', put it _after_ `/usr/bin'.
  244 +
  245 + On Haiku, software installed for all users goes in `/boot/common',
  246 +not `/usr/local'. It is recommended to use the following options:
  247 +
  248 + ./configure --prefix=/boot/common
  249 +
  250 +Specifying the System Type
  251 +==========================
  252 +
  253 + There may be some features `configure' cannot figure out
  254 +automatically, but needs to determine by the type of machine the package
  255 +will run on. Usually, assuming the package is built to be run on the
  256 +_same_ architectures, `configure' can figure that out, but if it prints
  257 +a message saying it cannot guess the machine type, give it the
  258 +`--build=TYPE' option. TYPE can either be a short name for the system
  259 +type, such as `sun4', or a canonical name which has the form:
  260 +
  261 + CPU-COMPANY-SYSTEM
  262 +
  263 +where SYSTEM can have one of these forms:
  264 +
  265 + OS
  266 + KERNEL-OS
  267 +
  268 + See the file `config.sub' for the possible values of each field. If
  269 +`config.sub' isn't included in this package, then this package doesn't
  270 +need to know the machine type.
  271 +
  272 + If you are _building_ compiler tools for cross-compiling, you should
  273 +use the option `--target=TYPE' to select the type of system they will
  274 +produce code for.
  275 +
  276 + If you want to _use_ a cross compiler, that generates code for a
  277 +platform different from the build platform, you should specify the
  278 +"host" platform (i.e., that on which the generated programs will
  279 +eventually be run) with `--host=TYPE'.
  280 +
  281 +Sharing Defaults
  282 +================
  283 +
  284 + If you want to set default values for `configure' scripts to share,
  285 +you can create a site shell script called `config.site' that gives
  286 +default values for variables like `CC', `cache_file', and `prefix'.
  287 +`configure' looks for `PREFIX/share/config.site' if it exists, then
  288 +`PREFIX/etc/config.site' if it exists. Or, you can set the
  289 +`CONFIG_SITE' environment variable to the location of the site script.
  290 +A warning: not all `configure' scripts look for a site script.
  291 +
  292 +Defining Variables
  293 +==================
  294 +
  295 + Variables not defined in a site shell script can be set in the
  296 +environment passed to `configure'. However, some packages may run
  297 +configure again during the build, and the customized values of these
  298 +variables may be lost. In order to avoid this problem, you should set
  299 +them in the `configure' command line, using `VAR=value'. For example:
  300 +
  301 + ./configure CC=/usr/local2/bin/gcc
  302 +
  303 +causes the specified `gcc' to be used as the C compiler (unless it is
  304 +overridden in the site shell script).
  305 +
  306 +Unfortunately, this technique does not work for `CONFIG_SHELL' due to
  307 +an Autoconf bug. Until the bug is fixed you can use this workaround:
  308 +
  309 + CONFIG_SHELL=/bin/bash /bin/bash ./configure CONFIG_SHELL=/bin/bash
  310 +
  311 +`configure' Invocation
  312 +======================
  313 +
  314 + `configure' recognizes the following options to control how it
  315 +operates.
  316 +
  317 +`--help'
  318 +`-h'
  319 + Print a summary of all of the options to `configure', and exit.
  320 +
  321 +`--help=short'
  322 +`--help=recursive'
  323 + Print a summary of the options unique to this package's
  324 + `configure', and exit. The `short' variant lists options used
  325 + only in the top level, while the `recursive' variant lists options
  326 + also present in any nested packages.
  327 +
  328 +`--version'
  329 +`-V'
  330 + Print the version of Autoconf used to generate the `configure'
  331 + script, and exit.
  332 +
  333 +`--cache-file=FILE'
  334 + Enable the cache: use and save the results of the tests in FILE,
  335 + traditionally `config.cache'. FILE defaults to `/dev/null' to
  336 + disable caching.
  337 +
  338 +`--config-cache'
  339 +`-C'
  340 + Alias for `--cache-file=config.cache'.
  341 +
  342 +`--quiet'
  343 +`--silent'
  344 +`-q'
  345 + Do not print messages saying which checks are being made. To
  346 + suppress all normal output, redirect it to `/dev/null' (any error
  347 + messages will still be shown).
  348 +
  349 +`--srcdir=DIR'
  350 + Look for the package's source code in directory DIR. Usually
  351 + `configure' can determine that directory automatically.
  352 +
  353 +`--prefix=DIR'
  354 + Use DIR as the installation prefix. *note Installation Names::
  355 + for more details, including other options available for fine-tuning
  356 + the installation locations.
  357 +
  358 +`--no-create'
  359 +`-n'
  360 + Run the configure checks, but stop before creating any output
  361 + files.
  362 +
  363 +`configure' also accepts some other, not widely useful, options. Run
  364 +`configure --help' for more details.
  365 +
1  NEWS
... ... @@ -0,0 +1 @@
  1 +Visit http://xbmc.org/ for all XBMC related news.
2  README
... ... @@ -0,0 +1,2 @@
  1 +See README.linux or README.osx depending on your platform. Ubuntu users can
  2 +check README.ubuntu for extra information.
5 configure.in
@@ -6,6 +6,7 @@ AC_INIT("xbmc", 9.11, http://trac.xbmc.org)
6 6 AC_CONFIG_HEADERS([config.h])
7 7 AH_TOP([#pragma once])
8 8
  9 +AM_INIT_AUTOMAKE
9 10 AC_CANONICAL_HOST
10 11
11 12 # General message strings
@@ -1064,6 +1065,10 @@ if test "$host_vendor" = "apple"; then
1064 1065 xbmc/cores/paplayer/FLACCodec/Makefile"
1065 1066 fi
1066 1067
  1068 +# Line below is used so we can use AM_INIT_AUTOMAKE. The corresponding
  1069 +# .dummy.am does nothing.
  1070 +AC_CONFIG_FILES([.dummy])
  1071 +
1067 1072 AC_CONFIG_FILES([${OUTPUT_FILES}])
1068 1073 AC_SUBST(CFLAGS)
1069 1074 AC_SUBST(CXXFLAGS)
376 missing
... ... @@ -0,0 +1,376 @@
  1 +#! /bin/sh
  2 +# Common stub for a few missing GNU programs while installing.
  3 +
  4 +scriptversion=2009-04-28.21; # UTC
  5 +
  6 +# Copyright (C) 1996, 1997, 1999, 2000, 2002, 2003, 2004, 2005, 2006,
  7 +# 2008, 2009 Free Software Foundation, Inc.
  8 +# Originally by Fran,cois Pinard <pinard@iro.umontreal.ca>, 1996.
  9 +
  10 +# This program is free software; you can redistribute it and/or modify
  11 +# it under the terms of the GNU General Public License as published by
  12 +# the Free Software Foundation; either version 2, or (at your option)
  13 +# any later version.
  14 +
  15 +# This program is distributed in the hope that it will be useful,
  16 +# but WITHOUT ANY WARRANTY; without even the implied warranty of
  17 +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
  18 +# GNU General Public License for more details.
  19 +
  20 +# You should have received a copy of the GNU General Public License
  21 +# along with this program. If not, see <http://www.gnu.org/licenses/>.
  22 +
  23 +# As a special exception to the GNU General Public License, if you
  24 +# distribute this file as part of a program that contains a
  25 +# configuration script generated by Autoconf, you may include it under
  26 +# the same distribution terms that you use for the rest of that program.
  27 +
  28 +if test $# -eq 0; then
  29 + echo 1>&2 "Try \`$0 --help' for more information"
  30 + exit 1
  31 +fi
  32 +
  33 +run=:
  34 +sed_output='s/.* --output[ =]\([^ ]*\).*/\1/p'
  35 +sed_minuso='s/.* -o \([^ ]*\).*/\1/p'
  36 +
  37 +# In the cases where this matters, `missing' is being run in the
  38 +# srcdir already.
  39 +if test -f configure.ac; then
  40 + configure_ac=configure.ac
  41 +else
  42 + configure_ac=configure.in
  43 +fi
  44 +
  45 +msg="missing on your system"
  46 +
  47 +case $1 in
  48 +--run)
  49 + # Try to run requested program, and just exit if it succeeds.
  50 + run=
  51 + shift
  52 + "$@" && exit 0
  53 + # Exit code 63 means version mismatch. This often happens
  54 + # when the user try to use an ancient version of a tool on
  55 + # a file that requires a minimum version. In this case we
  56 + # we should proceed has if the program had been absent, or
  57 + # if --run hadn't been passed.
  58 + if test $? = 63; then
  59 + run=:
  60 + msg="probably too old"
  61 + fi
  62 + ;;
  63 +
  64 + -h|--h|--he|--hel|--help)
  65 + echo "\
  66 +$0 [OPTION]... PROGRAM [ARGUMENT]...
  67 +
  68 +Handle \`PROGRAM [ARGUMENT]...' for when PROGRAM is missing, or return an
  69 +error status if there is no known handling for PROGRAM.
  70 +
  71 +Options:
  72 + -h, --help display this help and exit
  73 + -v, --version output version information and exit
  74 + --run try to run the given command, and emulate it if it fails
  75 +
  76 +Supported PROGRAM values:
  77 + aclocal touch file \`aclocal.m4'
  78 + autoconf touch file \`configure'
  79 + autoheader touch file \`config.h.in'
  80 + autom4te touch the output file, or create a stub one
  81 + automake touch all \`Makefile.in' files
  82 + bison create \`y.tab.[ch]', if possible, from existing .[ch]
  83 + flex create \`lex.yy.c', if possible, from existing .c
  84 + help2man touch the output file
  85 + lex create \`lex.yy.c', if possible, from existing .c
  86 + makeinfo touch the output file
  87 + tar try tar, gnutar, gtar, then tar without non-portable flags
  88 + yacc create \`y.tab.[ch]', if possible, from existing .[ch]
  89 +
  90 +Version suffixes to PROGRAM as well as the prefixes \`gnu-', \`gnu', and
  91 +\`g' are ignored when checking the name.
  92 +
  93 +Send bug reports to <bug-automake@gnu.org>."
  94 + exit $?
  95 + ;;
  96 +
  97 + -v|--v|--ve|--ver|--vers|--versi|--versio|--version)
  98 + echo "missing $scriptversion (GNU Automake)"
  99 + exit $?
  100 + ;;
  101 +
  102 + -*)
  103 + echo 1>&2 "$0: Unknown \`$1' option"
  104 + echo 1>&2 "Try \`$0 --help' for more information"
  105 + exit 1
  106 + ;;
  107 +
  108 +esac
  109 +
  110 +# normalize program name to check for.
  111 +program=`echo "$1" | sed '
  112 + s/^gnu-//; t
  113 + s/^gnu//; t
  114 + s/^g//; t'`
  115 +
  116 +# Now exit if we have it, but it failed. Also exit now if we
  117 +# don't have it and --version was passed (most likely to detect
  118 +# the program). This is about non-GNU programs, so use $1 not
  119 +# $program.
  120 +case $1 in
  121 + lex*|yacc*)
  122 + # Not GNU programs, they don't have --version.
  123 + ;;
  124 +
  125 + tar*)
  126 + if test -n "$run"; then
  127 + echo 1>&2 "ERROR: \`tar' requires --run"
  128 + exit 1
  129 + elif test "x$2" = "x--version" || test "x$2" = "x--help"; then
  130 + exit 1
  131 + fi
  132 + ;;
  133 +
  134 + *)
  135 + if test -z "$run" && ($1 --version) > /dev/null 2>&1; then
  136 + # We have it, but it failed.
  137 + exit 1
  138 + elif test "x$2" = "x--version" || test "x$2" = "x--help"; then
  139 + # Could not run --version or --help. This is probably someone
  140 + # running `$TOOL --version' or `$TOOL --help' to check whether
  141 + # $TOOL exists and not knowing $TOOL uses missing.
  142 + exit 1
  143 + fi
  144 + ;;
  145 +esac
  146 +
  147 +# If it does not exist, or fails to run (possibly an outdated version),
  148 +# try to emulate it.
  149 +case $program in
  150 + aclocal*)
  151 + echo 1>&2 "\
  152 +WARNING: \`$1' is $msg. You should only need it if
  153 + you modified \`acinclude.m4' or \`${configure_ac}'. You might want
  154 + to install the \`Automake' and \`Perl' packages. Grab them from
  155 + any GNU archive site."
  156 + touch aclocal.m4
  157 + ;;
  158 +
  159 + autoconf*)
  160 + echo 1>&2 "\
  161 +WARNING: \`$1' is $msg. You should only need it if
  162 + you modified \`${configure_ac}'. You might want to install the
  163 + \`Autoconf' and \`GNU m4' packages. Grab them from any GNU
  164 + archive site."
  165 + touch configure
  166 + ;;
  167 +
  168 + autoheader*)
  169 + echo 1>&2 "\
  170 +WARNING: \`$1' is $msg. You should only need it if
  171 + you modified \`acconfig.h' or \`${configure_ac}'. You might want
  172 + to install the \`Autoconf' and \`GNU m4' packages. Grab them
  173 + from any GNU archive site."
  174 + files=`sed -n 's/^[ ]*A[CM]_CONFIG_HEADER(\([^)]*\)).*/\1/p' ${configure_ac}`
  175 + test -z "$files" && files="config.h"
  176 + touch_files=
  177 + for f in $files; do
  178 + case $f in
  179 + *:*) touch_files="$touch_files "`echo "$f" |
  180 + sed -e 's/^[^:]*://' -e 's/:.*//'`;;
  181 + *) touch_files="$touch_files $f.in";;
  182 + esac
  183 + done
  184 + touch $touch_files
  185 + ;;
  186 +
  187 + automake*)
  188 + echo 1>&2 "\
  189 +WARNING: \`$1' is $msg. You should only need it if
  190 + you modified \`Makefile.am', \`acinclude.m4' or \`${configure_ac}'.
  191 + You might want to install the \`Automake' and \`Perl' packages.
  192 + Grab them from any GNU archive site."
  193 + find . -type f -name Makefile.am -print |
  194 + sed 's/\.am$/.in/' |
  195 + while read f; do touch "$f"; done
  196 + ;;
  197 +
  198 + autom4te*)
  199 + echo 1>&2 "\
  200 +WARNING: \`$1' is needed, but is $msg.
  201 + You might have modified some files without having the
  202 + proper tools for further handling them.
  203 + You can get \`$1' as part of \`Autoconf' from any GNU
  204 + archive site."
  205 +
  206 + file=`echo "$*" | sed -n "$sed_output"`
  207 + test -z "$file" && file=`echo "$*" | sed -n "$sed_minuso"`
  208 + if test -f "$file"; then
  209 + touch $file
  210 + else
  211 + test -z "$file" || exec >$file
  212 + echo "#! /bin/sh"
  213 + echo "# Created by GNU Automake missing as a replacement of"
  214 + echo "# $ $@"
  215 + echo "exit 0"
  216 + chmod +x $file
  217 + exit 1
  218 + fi
  219 + ;;
  220 +
  221 + bison*|yacc*)
  222 + echo 1>&2 "\
  223 +WARNING: \`$1' $msg. You should only need it if
  224 + you modified a \`.y' file. You may need the \`Bison' package
  225 + in order for those modifications to take effect. You can get
  226 + \`Bison' from any GNU archive site."
  227 + rm -f y.tab.c y.tab.h
  228 + if test $# -ne 1; then
  229 + eval LASTARG="\${$#}"
  230 + case $LASTARG in
  231 + *.y)
  232 + SRCFILE=`echo "$LASTARG" | sed 's/y$/c/'`
  233 + if test -f "$SRCFILE"; then
  234 + cp "$SRCFILE" y.tab.c
  235 + fi
  236 + SRCFILE=`echo "$LASTARG" | sed 's/y$/h/'`
  237 + if test -f "$SRCFILE"; then
  238 + cp "$SRCFILE" y.tab.h
  239 + fi
  240 + ;;
  241 + esac
  242 + fi
  243 + if test ! -f y.tab.h; then
  244 + echo >y.tab.h
  245 + fi
  246 + if test ! -f y.tab.c; then
  247 + echo 'main() { return 0; }' >y.tab.c
  248 + fi
  249 + ;;
  250 +
  251 + lex*|flex*)
  252 + echo 1>&2 "\
  253 +WARNING: \`$1' is $msg. You should only need it if
  254 + you modified a \`.l' file. You may need the \`Flex' package
  255 + in order for those modifications to take effect. You can get
  256 + \`Flex' from any GNU archive site."
  257 + rm -f lex.yy.c
  258 + if test $# -ne 1; then
  259 + eval LASTARG="\${$#}"
  260 + case $LASTARG in
  261 + *.l)
  262 + SRCFILE=`echo "$LASTARG" | sed 's/l$/c/'`
  263 + if test -f "$SRCFILE"; then
  264 + cp "$SRCFILE" lex.yy.c
  265 + fi
  266 + ;;
  267 + esac
  268 + fi
  269 + if test ! -f lex.yy.c; then
  270 + echo 'main() { return 0; }' >lex.yy.c
  271 + fi
  272 + ;;
  273 +
  274 + help2man*)
  275 + echo 1>&2 "\
  276 +WARNING: \`$1' is $msg. You should only need it if
  277 + you modified a dependency of a manual page. You may need the
  278 + \`Help2man' package in order for those modifications to take
  279 + effect. You can get \`Help2man' from any GNU archive site."
  280 +
  281 + file=`echo "$*" | sed -n "$sed_output"`
  282 + test -z "$file" && file=`echo "$*" | sed -n "$sed_minuso"`
  283 + if test -f "$file"; then
  284 + touch $file
  285 + else
  286 + test -z "$file" || exec >$file
  287 + echo ".ab help2man is required to generate this page"
  288 + exit $?
  289 + fi
  290 + ;;
  291 +
  292 + makeinfo*)
  293 + echo 1>&2 "\
  294 +WARNING: \`$1' is $msg. You should only need it if
  295 + you modified a \`.texi' or \`.texinfo' file, or any other file
  296 + indirectly affecting the aspect of the manual. The spurious
  297 + call might also be the consequence of using a buggy \`make' (AIX,
  298 + DU, IRIX). You might want to install the \`Texinfo' package or
  299 + the \`GNU make' package. Grab either from any GNU archive site."
  300 + # The file to touch is that specified with -o ...
  301 + file=`echo "$*" | sed -n "$sed_output"`
  302 + test -z "$file" && file=`echo "$*" | sed -n "$sed_minuso"`
  303 + if test -z "$file"; then
  304 + # ... or it is the one specified with @setfilename ...
  305 + infile=`echo "$*" | sed 's/.* \([^ ]*\) *$/\1/'`
  306 + file=`sed -n '
  307 + /^@setfilename/{
  308 + s/.* \([^ ]*\) *$/\1/
  309 + p
  310 + q
  311 + }' $infile`
  312 + # ... or it is derived from the source name (dir/f.texi becomes f.info)
  313 + test -z "$file" && file=`echo "$infile" | sed 's,.*/,,;s,.[^.]*$,,'`.info
  314 + fi
  315 + # If the file does not exist, the user really needs makeinfo;
  316 + # let's fail without touching anything.
  317 + test -f $file || exit 1
  318 + touch $file
  319 + ;;
  320 +
  321 + tar*)
  322 + shift
  323 +
  324 + # We have already tried tar in the generic part.
  325 + # Look for gnutar/gtar before invocation to avoid ugly error
  326 + # messages.
  327 + if (gnutar --version > /dev/null 2>&1); then
  328 + gnutar "$@" && exit 0
  329 + fi
  330 + if (gtar --version > /dev/null 2>&1); then
  331 + gtar "$@" && exit 0
  332 + fi
  333 + firstarg="$1"
  334 + if shift; then
  335 + case $firstarg in
  336 + *o*)
  337 + firstarg=`echo "$firstarg" | sed s/o//`
  338 + tar "$firstarg" "$@" && exit 0
  339 + ;;
  340 + esac
  341 + case $firstarg in
  342 + *h*)
  343 + firstarg=`echo "$firstarg" | sed s/h//`
  344 + tar "$firstarg" "$@" && exit 0
  345 + ;;
  346 + esac
  347 + fi
  348 +
  349 + echo 1>&2 "\
  350 +WARNING: I can't seem to be able to run \`tar' with the given arguments.
  351 + You may want to install GNU tar or Free paxutils, or check the
  352 + command line arguments."
  353 + exit 1
  354 + ;;
  355 +
  356 + *)
  357 + echo 1>&2 "\
  358 +WARNING: \`$1' is needed, and is $msg.
  359 + You might have modified some files without having the
  360 + proper tools for further handling them. Check the \`README' file,
  361 + it often tells you about the needed prerequisites for installing
  362 + this package. You may also peek at any GNU archive site, in case
  363 + some other package would contain this missing \`$1' program."
  364 + exit 1
  365 + ;;
  366 +esac
  367 +
  368 +exit 0
  369 +
  370 +# Local variables:
  371 +# eval: (add-hook 'write-file-hooks 'time-stamp)
  372 +# time-stamp-start: "scriptversion="
  373 +# time-stamp-format: "%:y-%02m-%02d.%02H"
  374 +# time-stamp-time-zone: "UTC"
  375 +# time-stamp-end: "; # UTC"
  376 +# End:

0 comments on commit 2cc3456

Please sign in to comment.
Something went wrong with that request. Please try again.