From 08af80bdd22cb9a55a0f840f2c240b2bda8c8577 Mon Sep 17 00:00:00 2001 From: Paolo Bonzini Date: Wed, 16 Jan 2008 08:54:37 +0100 Subject: [PATCH] commit new .gitignore files produced by autoboot --- .gitignore | 7 +- INSTALL | 236 ------------------------------------------- build-aux/.gitignore | 67 ++++++------ lib/.gitignore | 28 +++++ po/.gitignore | 1 + po/Makevars | 41 -------- 6 files changed, 67 insertions(+), 313 deletions(-) delete mode 100644 INSTALL delete mode 100644 po/Makevars diff --git a/.gitignore b/.gitignore index d42957b..b0a348c 100644 --- a/.gitignore +++ b/.gitignore @@ -1,16 +1,17 @@ +*~ +* ABOUT-NLS +INSTALL Makefile.in aclocal.m4 autom4te.cache -config_h.in -configure config.guess config.rpath config.sub +config_h.in +configure depcomp gnulib intl mdate-sh missing -*~ diff --git a/INSTALL b/INSTALL deleted file mode 100644 index 23e5f25..0000000 --- a/INSTALL +++ /dev/null @@ -1,236 +0,0 @@ -Installation Instructions -************************* - -Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free -Software Foundation, Inc. - -This file is free documentation; the Free Software Foundation gives -unlimited permission to copy, distribute and modify it. - -Basic Installation -================== - -These are generic installation instructions. - - The `configure' shell script attempts to guess correct values for -various system-dependent variables used during compilation. It uses -those values to create a `Makefile' in each directory of the package. -It may also create one or more `.h' files containing system-dependent -definitions. Finally, it creates a shell script `config.status' that -you can run in the future to recreate the current configuration, and a -file `config.log' containing compiler output (useful mainly for -debugging `configure'). - - It can also use an optional file (typically called `config.cache' -and enabled with `--cache-file=config.cache' or simply `-C') that saves -the results of its tests to speed up reconfiguring. (Caching is -disabled by default to prevent problems with accidental use of stale -cache files.) - - If you need to do unusual things to compile the package, please try -to figure out how `configure' could check whether to do them, and mail -diffs or instructions to the address given in the `README' so they can -be considered for the next release. If you are using the cache, and at -some point `config.cache' contains results you don't want to keep, you -may remove or edit it. - - The file `configure.ac' (or `configure.in') is used to create -`configure' by a program called `autoconf'. You only need -`configure.ac' if you want to change it or regenerate `configure' using -a newer version of `autoconf'. - -The simplest way to compile this package is: - - 1. `cd' to the directory containing the package's source code and type - `./configure' to configure the package for your system. If you're - using `csh' on an old version of System V, you might need to type - `sh ./configure' instead to prevent `csh' from trying to execute - `configure' itself. - - Running `configure' takes awhile. While running, it prints some - messages telling which features it is checking for. - - 2. Type `make' to compile the package. - - 3. Optionally, type `make check' to run any self-tests that come with - the package. - - 4. Type `make install' to install the programs and any data files and - documentation. - - 5. You can remove the program binaries and object files from the - source code directory by typing `make clean'. To also remove the - files that `configure' created (so you can compile the package for - a different kind of computer), type `make distclean'. There is - also a `make maintainer-clean' target, but that is intended mainly - for the package's developers. If you use it, you may have to get - all sorts of other programs in order to regenerate files that came - with the distribution. - -Compilers and Options -===================== - -Some systems require unusual options for compilation or linking that the -`configure' script does not know about. Run `./configure --help' for -details on some of the pertinent environment variables. - - You can give `configure' initial values for configuration parameters -by setting variables in the command line or in the environment. Here -is an example: - - ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix - - *Note Defining Variables::, for more details. - -Compiling For Multiple Architectures -==================================== - -You can compile the package for more than one kind of computer at the -same time, by placing the object files for each architecture in their -own directory. To do this, you must use a version of `make' that -supports the `VPATH' variable, such as GNU `make'. `cd' to the -directory where you want the object files and executables to go and run -the `configure' script. `configure' automatically checks for the -source code in the directory that `configure' is in and in `..'. - - If you have to use a `make' that does not support the `VPATH' -variable, you have to compile the package for one architecture at a -time in the source code directory. After you have installed the -package for one architecture, use `make distclean' before reconfiguring -for another architecture. - -Installation Names -================== - -By default, `make install' installs the package's commands under -`/usr/local/bin', include files under `/usr/local/include', etc. You -can specify an installation prefix other than `/usr/local' by giving -`configure' the option `--prefix=PREFIX'. - - You can specify separate installation prefixes for -architecture-specific files and architecture-independent files. If you -pass the option `--exec-prefix=PREFIX' to `configure', the package uses -PREFIX as the prefix for installing programs and libraries. -Documentation and other data files still use the regular prefix. - - In addition, if you use an unusual directory layout you can give -options like `--bindir=DIR' to specify different values for particular -kinds of files. Run `configure --help' for a list of the directories -you can set and what kinds of files go in them. - - If the package supports it, you can cause programs to be installed -with an extra prefix or suffix on their names by giving `configure' the -option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'. - -Optional Features -================= - -Some packages pay attention to `--enable-FEATURE' options to -`configure', where FEATURE indicates an optional part of the package. -They may also pay attention to `--with-PACKAGE' options, where PACKAGE -is something like `gnu-as' or `x' (for the X Window System). The -`README' should mention any `--enable-' and `--with-' options that the -package recognizes. - - For packages that use the X Window System, `configure' can usually -find the X include and library files automatically, but if it doesn't, -you can use the `configure' options `--x-includes=DIR' and -`--x-libraries=DIR' to specify their locations. - -Specifying the System Type -========================== - -There may be some features `configure' cannot figure out automatically, -but needs to determine by the type of machine the package will run on. -Usually, assuming the package is built to be run on the _same_ -architectures, `configure' can figure that out, but if it prints a -message saying it cannot guess the machine type, give it the -`--build=TYPE' option. TYPE can either be a short name for the system -type, such as `sun4', or a canonical name which has the form: - - CPU-COMPANY-SYSTEM - -where SYSTEM can have one of these forms: - - OS KERNEL-OS - - See the file `config.sub' for the possible values of each field. If -`config.sub' isn't included in this package, then this package doesn't -need to know the machine type. - - If you are _building_ compiler tools for cross-compiling, you should -use the option `--target=TYPE' to select the type of system they will -produce code for. - - If you want to _use_ a cross compiler, that generates code for a -platform different from the build platform, you should specify the -"host" platform (i.e., that on which the generated programs will -eventually be run) with `--host=TYPE'. - -Sharing Defaults -================ - -If you want to set default values for `configure' scripts to share, you -can create a site shell script called `config.site' that gives default -values for variables like `CC', `cache_file', and `prefix'. -`configure' looks for `PREFIX/share/config.site' if it exists, then -`PREFIX/etc/config.site' if it exists. Or, you can set the -`CONFIG_SITE' environment variable to the location of the site script. -A warning: not all `configure' scripts look for a site script. - -Defining Variables -================== - -Variables not defined in a site shell script can be set in the -environment passed to `configure'. However, some packages may run -configure again during the build, and the customized values of these -variables may be lost. In order to avoid this problem, you should set -them in the `configure' command line, using `VAR=value'. For example: - - ./configure CC=/usr/local2/bin/gcc - -causes the specified `gcc' to be used as the C compiler (unless it is -overridden in the site shell script). Here is a another example: - - /bin/bash ./configure CONFIG_SHELL=/bin/bash - -Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent -configuration-related scripts to be executed by `/bin/bash'. - -`configure' Invocation -====================== - -`configure' recognizes the following options to control how it operates. - -`--help' -`-h' - Print a summary of the options to `configure', and exit. - -`--version' -`-V' - Print the version of Autoconf used to generate the `configure' - script, and exit. - -`--cache-file=FILE' - Enable the cache: use and save the results of the tests in FILE, - traditionally `config.cache'. FILE defaults to `/dev/null' to - disable caching. - -`--config-cache' -`-C' - Alias for `--cache-file=config.cache'. - -`--quiet' -`--silent' -`-q' - Do not print messages saying which checks are being made. To - suppress all normal output, redirect it to `/dev/null' (any error - messages will still be shown). - -`--srcdir=DIR' - Look for the package's source code in directory DIR. Usually - `configure' can determine that directory automatically. - -`configure' also accepts some other, not widely useful, options. Run -`configure --help' for more details. - diff --git a/build-aux/.gitignore b/build-aux/.gitignore index 109f952..c256a3d 100644 --- a/build-aux/.gitignore +++ b/build-aux/.gitignore @@ -1,39 +1,8 @@ -codeset.m4 -gettext.m4 -glibc2.m4 -glibc21.m4 -gnulib-comp.m4 -iconv.m4 -install-sh -intdiv0.m4 -intmax.m4 -inttypes-h.m4 -inttypes-pri.m4 -inttypes_h.m4 -lcmessage.m4 -lib-ld.m4 -lib-link.m4 -lib-prefix.m4 -lock.m4 -longdouble.m4 -longlong.m4 -nls.m4 -po.m4 -printf-posix.m4 -progtest.m4 -signed.m4 -size_max.m4 -stdint_h.m4 -texinfo.tex -uintmax_t.m4 -ulonglong.m4 -visibility.m4 -wchar_t.m4 -wint_t.m4 -xsize.m4 absolute-header.m4 acl.m4 alloca.m4 +codeset.m4 +config.rpath eoverflow.m4 error.m4 exitfail.m4 @@ -42,17 +11,35 @@ float_h.m4 getdelim.m4 getline.m4 getopt.m4 +gettext.m4 gettimeofday.m4 +glibc2.m4 +glibc21.m4 gnulib-common.m4 +gnulib-comp.m4 gnulib-tool.m4 +iconv.m4 include_next.m4 inline.m4 +install-sh +intdiv0.m4 intl.m4 intldir.m4 intlmacosx.m4 +intmax.m4 intmax_t.m4 +inttypes-h.m4 +inttypes-pri.m4 +inttypes_h.m4 +lcmessage.m4 +lib-ld.m4 +lib-link.m4 +lib-prefix.m4 link-warning.h localcharset.m4 +lock.m4 +longdouble.m4 +longlong.m4 malloc.m4 mbrtowc.m4 mbstate_t.m4 @@ -60,13 +47,20 @@ memchr.m4 memcmp.m4 memmove.m4 mkstemp.m4 +nls.m4 pathmax.m4 +po.m4 +printf-posix.m4 +progtest.m4 quote.m4 quotearg.m4 realloc.m4 +signed.m4 +size_max.m4 snprintf.m4 stdbool.m4 stdint.m4 +stdint_h.m4 stdio_h.m4 stdlib_h.m4 strerror.m4 @@ -74,9 +68,16 @@ strverscmp.m4 sys_stat_h.m4 sys_time_h.m4 tempname.m4 +texinfo.tex +uintmax_t.m4 +ulonglong.m4 unistd_h.m4 unlocked-io.m4 vasnprintf.m4 +visibility.m4 wchar.m4 +wchar_t.m4 wctype.m4 +wint_t.m4 xalloc.m4 +xsize.m4 diff --git a/lib/.gitignore b/lib/.gitignore index f6ef3c5..001f458 100644 --- a/lib/.gitignore +++ b/lib/.gitignore @@ -3,6 +3,8 @@ acl.c acl.h acl_entries.c alloca.c +alloca.h +alloca.in.h alloca_.h asnprintf.c config.charset @@ -12,16 +14,21 @@ exitfail.c exitfail.h file-has-acl.c float+.h +float.h +float.in.h float_.h getdelim.c getline.c getopt.c +getopt.h +getopt.in.h getopt1.c getopt_.h getopt_int.h gettext.h gettimeofday.c gnulib.mk +intprops.h localcharset.c localcharset.h memchr.c @@ -45,23 +52,44 @@ ref-del.sin size_max.h snprintf.c stat-macros.h +stdbool.h +stdbool.in.h stdbool_.h +stdint.h +stdint.in.h stdint_.h +stdio.h +stdio.in.h stdio_.h +stdlib.h +stdlib.in.h stdlib_.h strerror.c +string.h +string.in.h strverscmp.c strverscmp.h +sys +sys_stat.h +sys_stat.in.h sys_stat_.h +sys_time.h +sys_time.in.h sys_time_.h tempname.c tempname.h +unistd.h +unistd.in.h unistd_.h unlocked-io.h vasnprintf.c vasnprintf.h verify.h +wchar.h +wchar.in.h wchar_.h +wctype.h +wctype.in.h wctype_.h xalloc-die.c xalloc.h diff --git a/po/.gitignore b/po/.gitignore index f72626a..52ad320 100644 --- a/po/.gitignore +++ b/po/.gitignore @@ -1,5 +1,6 @@ LINGUAS Makefile.in.in +Makevars Makevars.template Rules-quot boldquot.sed diff --git a/po/Makevars b/po/Makevars deleted file mode 100644 index 32692ab..0000000 --- a/po/Makevars +++ /dev/null @@ -1,41 +0,0 @@ -# Makefile variables for PO directory in any package using GNU gettext. - -# Usually the message domain is the same as the package name. -DOMAIN = $(PACKAGE) - -# These two variables depend on the location of this directory. -subdir = po -top_builddir = .. - -# These options get passed to xgettext. -XGETTEXT_OPTIONS = --keyword=_ --keyword=N_ - -# This is the copyright holder that gets inserted into the header of the -# $(DOMAIN).pot file. Set this to the copyright holder of the surrounding -# package. (Note that the msgstr strings, extracted from the package's -# sources, belong to the copyright holder of the package.) Translators are -# expected to transfer the copyright for their translations to this person -# or entity, or to disclaim their copyright. The empty string stands for -# the public domain; in this case the translators are expected to disclaim -# their copyright. -COPYRIGHT_HOLDER = Free Software Foundation, Inc. - -# This is the email address or URL to which the translators shall report -# bugs in the untranslated strings: -# - Strings which are not entire sentences, see the maintainer guidelines -# in the GNU gettext documentation, section 'Preparing Strings'. -# - Strings which use unclear terms or require additional context to be -# understood. -# - Strings which make invalid assumptions about notation of date, time or -# money. -# - Pluralisation problems. -# - Incorrect English spelling. -# - Incorrect formatting. -# It can be your email address, or a mailing list address where translators -# can write to without being subscribed, or the URL of a web page through -# which the translators can contact you. -MSGID_BUGS_ADDRESS = - -# This is the list of locale categories, beyond LC_MESSAGES, for which the -# message catalogs shall be used. It is usually empty. -EXTRA_LOCALE_CATEGORIES =