[Pinfo-devel] r15 - in pinfo/trunk: . po tools
Bas Zoetekouw
bas at costa.debian.org
Sat Jul 23 19:58:06 UTC 2005
Author: bas
Date: 2005-07-23 19:58:05 +0000 (Sat, 23 Jul 2005)
New Revision: 15
Removed:
pinfo/trunk/tools/config.guess
pinfo/trunk/tools/config.rpath
pinfo/trunk/tools/config.sub
pinfo/trunk/tools/depcomp
pinfo/trunk/tools/install-sh
pinfo/trunk/tools/ltmain.sh
pinfo/trunk/tools/missing
pinfo/trunk/tools/mkinstalldirs
pinfo/trunk/tools/texinfo.tex
Modified:
pinfo/trunk/COPYING
pinfo/trunk/INSTALL
pinfo/trunk/Makefile.in
pinfo/trunk/config.h.in
pinfo/trunk/po/Makefile.in.in
Log:
Ran autoreconf and removed the files that are generated and/or automatically
copied into the source tree
Modified: pinfo/trunk/COPYING
===================================================================
--- pinfo/trunk/COPYING 2005-07-23 19:34:57 UTC (rev 14)
+++ pinfo/trunk/COPYING 2005-07-23 19:58:05 UTC (rev 15)
@@ -2,7 +2,7 @@
Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc.
- 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
+ 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
@@ -291,7 +291,7 @@
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
- Copyright (C) 19yy <name of author>
+ Copyright (C) <year> <name of author>
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
@@ -313,7 +313,7 @@
If the program is interactive, make it output a short notice like this
when it starts in an interactive mode:
- Gnomovision version 69, Copyright (C) 19yy name of author
+ Gnomovision version 69, Copyright (C) year name of author
Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.
Modified: pinfo/trunk/INSTALL
===================================================================
--- pinfo/trunk/INSTALL 2005-07-23 19:34:57 UTC (rev 14)
+++ pinfo/trunk/INSTALL 2005-07-23 19:58:05 UTC (rev 15)
@@ -1,61 +1,229 @@
-INSTALL is a description, which is autogenerated from INSTALL.in template.
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002 Free Software
+Foundation, Inc.
-1. Installing from tarball distribution
+ This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
-- Untar pinfo tarball
-$ tar xzvf pinfo-0.6.8.tar.gz
-- Change dir to pinfo-0.6.8
-$ cd pinfo-0.6.8
-- run configure script
-$ ./configure
-- run make
-$ make
-- to install switch to root
-$ su -c 'make install'
+Basic Installation
+==================
-2. Building rpm package from tarball distribution
+ These are generic installation instructions.
-- build binary package
-$ rpm -tb pinfo-0.6.8.tar.gz
-- install binary package
-$ su -c "rpm -Uhv /path_to_RPMS_dir/pinfo-0.6.8-1.i386.rpm"
+ 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').
-3. Installing from CVS (not recommended -- there is ussualy a developmental
-version of package available, which may be unstable).
+ 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.)
-- Set your CVSROOT environment variable
-$ CVSROOT=":pserver:cvs at cvs.pld.org.pl:/cvsroot"; export CVSROOT
-- Login to CVS server
-$ cvs login
-(Logging in to cvs at cvs.pld.org.pl)
-CVS password: [Hit Enter]
-- Get source
-$ cvs co pinfo
-- Change dir to pinfo
-$ cd pinfo
-- Run autogen.sh script
-$ ./autogen.sh
-- Run make
-$ make
-- To install switch to root
-$ su -c 'make install'
+ 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.
-4. Building rpm package from CVS
+ 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'.
-- Set your CVSROOT environment variable
-$ CVSROOT=":pserver:cvs at cvs.pld.org.pl:/cvsroot"; export CVSROOT
-- Login to CVS server
-$ cvs login
-(Logging in to cvs at cvs.pld.org.pl)
-CVS password: [Hit Enter]
-- Get source
-$ cvs co pinfo
-- Change dir to pinfo
-$ cd pinfo
-- Run autogen.sh script
-$ ./autogen.sh
-- Build binary package
-$ make rpm
-- Install binary package
-$ su -c "rpm -Uhv /path_to_RPMS_dir/pinfo-0.6.8-1.i386.rpm"
+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' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PATH'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=PATH' 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 `--target=TYPE' option 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
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`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.
+
Modified: pinfo/trunk/Makefile.in
===================================================================
--- pinfo/trunk/Makefile.in 2005-07-23 19:34:57 UTC (rev 14)
+++ pinfo/trunk/Makefile.in 2005-07-23 19:58:05 UTC (rev 15)
@@ -184,7 +184,7 @@
check-recursive installcheck-recursive
DIST_COMMON = README $(srcdir)/Makefile.in $(srcdir)/configure \
ABOUT-NLS AUTHORS COPYING ChangeLog INSTALL Makefile.am NEWS \
- TODO aclocal.m4 config.h.in configure configure.ac depcomp \
+ TODO aclocal.m4 config.h.in configure configure.ac \
pinfo.spec.in tools/config.guess tools/config.rpath \
tools/config.sub tools/depcomp tools/install-sh tools/ltmain.sh \
tools/missing tools/mkinstalldirs tools/texinfo.tex
@@ -207,7 +207,7 @@
$(srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(srcdir)/configure.ac $(ACLOCAL_M4) $(CONFIGURE_DEPENDENCIES)
cd $(srcdir) && $(AUTOCONF)
-$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.ac macros/aclocal-include.m4 macros/compiler-flags.m4 macros/curses.m4 macros/readline.m4
+$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.ac macros/aclocal-include.m4 macros/codeset.m4 macros/compiler-flags.m4 macros/curses.m4 macros/gettext.m4 macros/glibc2.m4 macros/glibc21.m4 macros/iconv.m4 macros/intdiv0.m4 macros/intmax.m4 macros/inttypes-pri.m4 macros/inttypes.m4 macros/inttypes_h.m4 macros/isc-posix.m4 macros/lcmessage.m4 macros/lib-ld.m4 macros/lib-link.m4 macros/lib-prefix.m4 macros/longdouble.m4 macros/longlong.m4 macros/nls.m4 macros/po.m4 macros/printf-posix.m4 macros/progtest.m4 macros/readline.m4 macros/signed.m4 macros/size_max.m4 macros/stdint_h.m4 macros/uintmax_t.m4 macros/ulonglong.m4 macros/wchar_t.m4 macros/wint_t.m4 macros/xsize.m4
cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
config.h: stamp-h1
Modified: pinfo/trunk/config.h.in
===================================================================
--- pinfo/trunk/config.h.in 2005-07-23 19:34:57 UTC (rev 14)
+++ pinfo/trunk/config.h.in 2005-07-23 19:58:05 UTC (rev 15)
@@ -200,6 +200,9 @@
/* Define to 1 if you have the <string.h> header file. */
#undef HAVE_STRING_H
+/* Define to 1 if you have the `strstr' function. */
+#undef HAVE_STRSTR
+
/* Define to 1 if you have the `strtoul' function. */
#undef HAVE_STRTOUL
Modified: pinfo/trunk/po/Makefile.in.in
===================================================================
--- pinfo/trunk/po/Makefile.in.in 2005-07-23 19:34:57 UTC (rev 14)
+++ pinfo/trunk/po/Makefile.in.in 2005-07-23 19:58:05 UTC (rev 15)
@@ -285,9 +285,8 @@
mostlyclean:
rm -f remove-potcdate.sed
- rm -f stamp-po
+ rm -f stamp-poT
rm -f core core.* $(DOMAIN).po $(DOMAIN).1po $(DOMAIN).2po *.new.po
- rm -f *.gmo
rm -fr *.o
clean: mostlyclean
Deleted: pinfo/trunk/tools/config.guess
Deleted: pinfo/trunk/tools/config.rpath
Deleted: pinfo/trunk/tools/config.sub
Deleted: pinfo/trunk/tools/depcomp
Deleted: pinfo/trunk/tools/install-sh
Deleted: pinfo/trunk/tools/ltmain.sh
Deleted: pinfo/trunk/tools/missing
Deleted: pinfo/trunk/tools/mkinstalldirs
Deleted: pinfo/trunk/tools/texinfo.tex
More information about the Pinfo-devel
mailing list