mirror of
https://git.savannah.gnu.org/git/emacs.git
synced 2024-11-21 06:55:39 +00:00
Quote 'like this' in top-level files
* CONTRIBUTE, INSTALL, Makefile.in, README, configure.ac, make-dist: Prefer to single-quote 'like this' (instead of the older style `like this'). * configure.ac: Fix some space-before-tab problems that 'git commit' complained about.
This commit is contained in:
Paul Eggert
parent
62e170072e
commit
9099d45df7
@ -146,7 +146,7 @@ The general format is as follows.
|
||||
a top-level ChangeLog file manually, and update it with 'C-x 4 a' as
|
||||
usual. Do not register the ChangeLog file under git; instead, use
|
||||
'C-c C-a' to insert its contents into into your *vc-log* buffer.
|
||||
Or if `log-edit-hook' includes `log-edit-insert-changelog' (which it
|
||||
Or if 'log-edit-hook' includes 'log-edit-insert-changelog' (which it
|
||||
does by default), they will be filled in for you automatically.
|
||||
|
||||
- Alternatively, you can use the vc-dwim command to maintain commit
|
||||
@ -236,7 +236,7 @@ the entry with "+++". Otherwise do not mark it.
|
||||
|
||||
Please see (info "(elisp)Documentation Tips") or
|
||||
https://www.gnu.org/software/emacs/manual/html_node/elisp/Documentation-Tips.html
|
||||
for more specific tips on Emacs's doc style. Use `checkdoc' to check
|
||||
for more specific tips on Emacs's doc style. Use 'checkdoc' to check
|
||||
for documentation errors before submitting a patch.
|
||||
|
||||
** Test your changes.
|
||||
|
||||
298
INSTALL
298
INSTALL
@ -13,21 +13,21 @@ msdos/INSTALL. For information about building from a repository checkout
|
||||
|
||||
BASIC INSTALLATION
|
||||
|
||||
On most Unix systems, you build Emacs by first running the `configure'
|
||||
On most Unix systems, you build Emacs by first running the 'configure'
|
||||
shell script. This attempts to deduce the correct values for
|
||||
various system-dependent variables and features, and find the
|
||||
directories where certain system headers and libraries are kept.
|
||||
In a few cases, you may need to explicitly tell configure where to
|
||||
find some things, or what options to use.
|
||||
|
||||
`configure' creates a `Makefile' in several subdirectories, and a
|
||||
`src/config.h' file containing system-dependent definitions.
|
||||
Running the `make' utility then builds the package for your system.
|
||||
'configure' creates a 'Makefile' in several subdirectories, and a
|
||||
'src/config.h' file containing system-dependent definitions.
|
||||
Running the 'make' utility then builds the package for your system.
|
||||
|
||||
Building Emacs requires GNU make, <http://www.gnu.org/software/make/>.
|
||||
On most systems that Emacs supports, this is the default `make' program.
|
||||
On most systems that Emacs supports, this is the default 'make' program.
|
||||
|
||||
Here's the procedure to build Emacs using `configure' on systems which
|
||||
Here's the procedure to build Emacs using 'configure' on systems which
|
||||
are supported by it. In some cases, if the simplified procedure fails,
|
||||
you might need to use various non-default options, and maybe perform
|
||||
some of the steps manually. The more detailed description in the other
|
||||
@ -40,48 +40,48 @@ sections if you need to.
|
||||
This includes the space-saving that comes from automatically
|
||||
compressing the Lisp source files on installation.
|
||||
|
||||
2a. `cd' to the directory where you unpacked Emacs and invoke the
|
||||
`configure' script:
|
||||
2a. 'cd' to the directory where you unpacked Emacs and invoke the
|
||||
'configure' script:
|
||||
|
||||
./configure
|
||||
|
||||
2b. Alternatively, create a separate directory, outside the source
|
||||
directory, where you want to build Emacs, and invoke `configure'
|
||||
directory, where you want to build Emacs, and invoke 'configure'
|
||||
from there:
|
||||
|
||||
SOURCE-DIR/configure
|
||||
|
||||
where SOURCE-DIR is the top-level Emacs source directory.
|
||||
|
||||
3. When `configure' finishes, it prints several lines of details
|
||||
3. When 'configure' finishes, it prints several lines of details
|
||||
about the system configuration. Read those details carefully
|
||||
looking for anything suspicious, such as wrong CPU and operating
|
||||
system names, wrong places for headers or libraries, missing
|
||||
libraries that you know are installed on your system, etc.
|
||||
|
||||
If you find anything wrong, you may have to pass to `configure'
|
||||
If you find anything wrong, you may have to pass to 'configure'
|
||||
one or more options specifying the explicit machine configuration
|
||||
name, where to find various headers and libraries, etc.
|
||||
Refer to the section DETAILED BUILDING AND INSTALLATION below.
|
||||
|
||||
If `configure' didn't find some image support libraries, such as
|
||||
If 'configure' didn't find some image support libraries, such as
|
||||
Xpm and jpeg, refer to "Image support libraries" below.
|
||||
|
||||
If the details printed by `configure' don't make any sense to
|
||||
you, but there are no obvious errors, assume that `configure' did
|
||||
If the details printed by 'configure' don't make any sense to
|
||||
you, but there are no obvious errors, assume that 'configure' did
|
||||
its job and proceed.
|
||||
|
||||
4. Invoke the `make' program:
|
||||
4. Invoke the 'make' program:
|
||||
|
||||
make
|
||||
|
||||
5. If `make' succeeds, it will build an executable program `emacs'
|
||||
in the `src' directory. You can try this program, to make sure
|
||||
5. If 'make' succeeds, it will build an executable program 'emacs'
|
||||
in the 'src' directory. You can try this program, to make sure
|
||||
it works:
|
||||
|
||||
src/emacs -Q
|
||||
|
||||
6. Assuming that the program `src/emacs' starts and displays its
|
||||
6. Assuming that the program 'src/emacs' starts and displays its
|
||||
opening screen, you can install the program and its auxiliary
|
||||
files into their installation directories:
|
||||
|
||||
@ -101,7 +101,7 @@ sections if you need to.
|
||||
make distclean
|
||||
|
||||
Note that the install automatically saves space by compressing
|
||||
(provided you have the `gzip' program) those installed Lisp source (.el)
|
||||
(provided you have the 'gzip' program) those installed Lisp source (.el)
|
||||
files that have corresponding .elc versions, as well as the Info files.
|
||||
|
||||
|
||||
@ -114,7 +114,7 @@ On GNU and Unix systems, Emacs needs the optional libraries "m17n-db",
|
||||
Indic and Khmer, and also for scripts that require Arabic shaping
|
||||
support (Arabic and Farsi). On some systems, particularly GNU/Linux,
|
||||
these libraries may be already present or available as additional
|
||||
packages. Note that if there is a separate `dev' or `devel' package,
|
||||
packages. Note that if there is a separate 'dev' or 'devel' package,
|
||||
for use at compilation time rather than run time, you will need that
|
||||
as well as the corresponding run time package; typically the dev
|
||||
package will contain header files and a library archive. Otherwise,
|
||||
@ -148,7 +148,7 @@ XBM images whose support is built-in.
|
||||
|
||||
On some systems, particularly on GNU/Linux, these libraries may
|
||||
already be present or available as additional packages. If
|
||||
there is a separate `dev' or `devel' package, for use at compilation
|
||||
there is a separate 'dev' or 'devel' package, for use at compilation
|
||||
time rather than run time, you will need that as well as the
|
||||
corresponding run time package; typically the dev package will
|
||||
contain header files and a library archive. Otherwise, you can
|
||||
@ -195,15 +195,15 @@ number of free Unicode fonts.
|
||||
Many GNU/Linux systems do not come with development packages by default;
|
||||
they include the files that you need to run Emacs, but not those you
|
||||
need to compile it. For example, to compile Emacs with support for X
|
||||
and graphics libraries, you may need to install the `X development'
|
||||
and graphics libraries, you may need to install the X development
|
||||
package(s), and development versions of the jpeg, png, etc. packages.
|
||||
|
||||
The names of the packages that you need varies according to the
|
||||
GNU/Linux distribution that you use, and the options that you want to
|
||||
configure Emacs with. On Debian-based systems, you can install all the
|
||||
packages needed to build the installed version of Emacs with a command
|
||||
like `apt-get build-dep emacs24'. On Red Hat systems, the
|
||||
corresponding command is `yum-builddep emacs'.
|
||||
like 'apt-get build-dep emacs24'. On Red Hat systems, the
|
||||
corresponding command is 'yum-builddep emacs'.
|
||||
|
||||
|
||||
DETAILED BUILDING AND INSTALLATION:
|
||||
@ -214,37 +214,37 @@ the file nt/INSTALL. For MS-DOS and MS Windows 3.X, see msdos/INSTALL.)
|
||||
|
||||
1) See the basic installation summary above for the disk space requirements.
|
||||
|
||||
2) In the unlikely event that `configure' does not detect your system
|
||||
type correctly, consult `./etc/MACHINES' to see what --host, --build
|
||||
options you should pass to `configure'. That file also offers hints
|
||||
2) In the unlikely event that 'configure' does not detect your system
|
||||
type correctly, consult './etc/MACHINES' to see what --host, --build
|
||||
options you should pass to 'configure'. That file also offers hints
|
||||
for getting around some possible installation problems.
|
||||
|
||||
3) You can build Emacs in the top-level Emacs source directory
|
||||
or in a separate directory.
|
||||
|
||||
3a) To build in the top-level Emacs source directory, go to that
|
||||
directory and run the program `configure' as follows:
|
||||
directory and run the program 'configure' as follows:
|
||||
|
||||
./configure [--OPTION[=VALUE]] ...
|
||||
|
||||
If `configure' cannot determine your system type, try again
|
||||
If 'configure' cannot determine your system type, try again
|
||||
specifying the proper --build, --host options explicitly.
|
||||
|
||||
If you don't want X support, specify `--with-x=no'. If you omit this
|
||||
option, `configure' will try to figure out for itself whether your
|
||||
If you don't want X support, specify '--with-x=no'. If you omit this
|
||||
option, 'configure' will try to figure out for itself whether your
|
||||
system has X, and arrange to use it if present.
|
||||
|
||||
The `--x-includes=DIR' and `--x-libraries=DIR' options tell the build
|
||||
The '--x-includes=DIR' and '--x-libraries=DIR' options tell the build
|
||||
process where the compiler should look for the include files and
|
||||
object libraries used with the X Window System. Normally, `configure'
|
||||
object libraries used with the X Window System. Normally, 'configure'
|
||||
is able to find them; these options are necessary if you have your X
|
||||
Window System files installed in unusual places. These options also
|
||||
accept a list of directories, separated with colons.
|
||||
|
||||
To get more attractive menus, you can specify an X toolkit when you
|
||||
configure Emacs; use the option `--with-x-toolkit=TOOLKIT', where
|
||||
TOOLKIT is `gtk' (the default), `athena', or `motif' (`yes' and
|
||||
`lucid' are synonyms for `athena'). Compiling with Motif causes a
|
||||
configure Emacs; use the option '--with-x-toolkit=TOOLKIT', where
|
||||
TOOLKIT is 'gtk' (the default), 'athena', or 'motif' ('yes' and
|
||||
'lucid' are synonyms for 'athena'). Compiling with Motif causes a
|
||||
standard File Selection Dialog to pop up when you invoke file commands
|
||||
with the mouse. You can get fancy 3D-style scroll bars, even without
|
||||
Gtk or Motif, if you have the Xaw3d library installed (see
|
||||
@ -257,12 +257,12 @@ Emacs will autolaunch a D-Bus session bus, when the environment
|
||||
variable DISPLAY is set, but no session bus is running. This might be
|
||||
inconvenient for Emacs when running as daemon or running via a remote
|
||||
ssh connection. In order to completely prevent the use of D-Bus, configure
|
||||
Emacs with the options `--without-dbus --without-gconf --without-gsettings'.
|
||||
Emacs with the options '--without-dbus --without-gconf --without-gsettings'.
|
||||
|
||||
The Emacs mail reader RMAIL is configured to be able to read mail from
|
||||
a POP3 server by default. Versions of the POP protocol older than
|
||||
POP3 are not supported. For Kerberos-authenticated POP add
|
||||
`--with-kerberos', for Hesiod support add `--with-hesiod'. While POP3
|
||||
'--with-kerberos', for Hesiod support add '--with-hesiod'. While POP3
|
||||
is always enabled, whether Emacs actually uses POP is controlled by
|
||||
individual users--see the Rmail chapter of the Emacs manual.
|
||||
|
||||
@ -322,28 +322,28 @@ that goes awry. 'make V=1' also enables the extra chatter.
|
||||
|
||||
Use --enable-link-time-optimization to enable link-time optimizer. If
|
||||
you're using GNU compiler, this feature is supported since version 4.5.0.
|
||||
If `configure' can determine number of online CPUS on your system, final
|
||||
If 'configure' can determine number of online CPUS on your system, final
|
||||
link-time optimization and code generation is executed in parallel using
|
||||
one job per each available online CPU.
|
||||
|
||||
This option is also supported for clang. You should have GNU binutils
|
||||
with `gold' linker and plugin support, and clang with LLVMgold.so plugin.
|
||||
with 'gold' linker and plugin support, and clang with LLVMgold.so plugin.
|
||||
Read http://llvm.org/docs/GoldPlugin.html for details. Also note that
|
||||
this feature is still experimental, so prepare to build binutils and
|
||||
clang from the corresponding source code repositories.
|
||||
|
||||
The `--prefix=PREFIXDIR' option specifies where the installation process
|
||||
should put emacs and its data files. This defaults to `/usr/local'.
|
||||
The '--prefix=PREFIXDIR' option specifies where the installation process
|
||||
should put emacs and its data files. This defaults to '/usr/local'.
|
||||
- Emacs (and the other utilities users run) go in PREFIXDIR/bin
|
||||
(unless the `--exec-prefix' option says otherwise).
|
||||
(unless the '--exec-prefix' option says otherwise).
|
||||
- The architecture-independent files go in PREFIXDIR/share/emacs/VERSION
|
||||
(where VERSION is the version number of Emacs, like `23.2').
|
||||
(where VERSION is the version number of Emacs, like '23.2').
|
||||
- The architecture-dependent files go in
|
||||
PREFIXDIR/libexec/emacs/VERSION/CONFIGURATION
|
||||
(where CONFIGURATION is the configuration name, like
|
||||
i686-pc-linux-gnu), unless the `--exec-prefix' option says otherwise.
|
||||
i686-pc-linux-gnu), unless the '--exec-prefix' option says otherwise.
|
||||
|
||||
The `--exec-prefix=EXECDIR' option allows you to specify a separate
|
||||
The '--exec-prefix=EXECDIR' option allows you to specify a separate
|
||||
portion of the directory tree for installing architecture-specific
|
||||
files, like executables and utility programs. If specified,
|
||||
- Emacs (and the other utilities users run) go in EXECDIR/bin, and
|
||||
@ -358,26 +358,26 @@ For example, the command
|
||||
configures Emacs to build for a 32-bit GNU/Linux distribution,
|
||||
without sound support.
|
||||
|
||||
`configure' doesn't do any compilation or installation itself.
|
||||
'configure' doesn't do any compilation or installation itself.
|
||||
It just creates the files that influence those things:
|
||||
`./Makefile' in the top-level directory and several subdirectories;
|
||||
and `./src/config.h'.
|
||||
'./Makefile' in the top-level directory and several subdirectories;
|
||||
and './src/config.h'.
|
||||
|
||||
When it is done, `configure' prints a description of what it did and
|
||||
creates a shell script `config.status' which, when run, recreates the
|
||||
same configuration. If `configure' exits with an error after
|
||||
disturbing the status quo, it removes `config.status'. `configure'
|
||||
also creates a file `config.cache' that saves the results of its tests
|
||||
to make reconfiguring faster, and a file `config.log' containing compiler
|
||||
output (useful mainly for debugging `configure'). You can give
|
||||
`configure' the option `--cache-file=FILE' to use the results of the
|
||||
tests in FILE instead of `config.cache'. Set FILE to `/dev/null' to
|
||||
disable caching, for debugging `configure'.
|
||||
When it is done, 'configure' prints a description of what it did and
|
||||
creates a shell script 'config.status' which, when run, recreates the
|
||||
same configuration. If 'configure' exits with an error after
|
||||
disturbing the status quo, it removes 'config.status'. 'configure'
|
||||
also creates a file 'config.cache' that saves the results of its tests
|
||||
to make reconfiguring faster, and a file 'config.log' containing compiler
|
||||
output (useful mainly for debugging 'configure'). You can give
|
||||
'configure' the option '--cache-file=FILE' to use the results of the
|
||||
tests in FILE instead of 'config.cache'. Set FILE to '/dev/null' to
|
||||
disable caching, for debugging 'configure'.
|
||||
|
||||
If the description of the system configuration printed by `configure'
|
||||
If the description of the system configuration printed by 'configure'
|
||||
is not right, or if it claims some of the features or libraries are not
|
||||
available when you know they are, look at the `config.log' file for
|
||||
the trace of the failed tests performed by `configure' to check
|
||||
available when you know they are, look at the 'config.log' file for
|
||||
the trace of the failed tests performed by 'configure' to check
|
||||
whether these features are supported. Typically, some test fails
|
||||
because the compiler cannot find some function in the system
|
||||
libraries, or some macro-processor definition in the system headers.
|
||||
@ -385,29 +385,29 @@ libraries, or some macro-processor definition in the system headers.
|
||||
Some tests might fail because the compiler should look in special
|
||||
directories for some header files, or link against optional
|
||||
libraries, or use special compilation options. You can force
|
||||
`configure' and the build process which follows it to do that by
|
||||
'configure' and the build process which follows it to do that by
|
||||
setting the variables CPPFLAGS, CFLAGS, LDFLAGS, LIBS, CPP and CC
|
||||
before running `configure'. CPP is the command which invokes the
|
||||
before running 'configure'. CPP is the command which invokes the
|
||||
preprocessor, CPPFLAGS lists the options passed to it, CFLAGS are
|
||||
compilation options, LDFLAGS are options used when linking, LIBS are
|
||||
libraries to link against, and CC is the command which invokes the
|
||||
compiler. By default, gcc is used if available.
|
||||
|
||||
Here's an example of a `configure' invocation, assuming a Bourne-like
|
||||
Here's an example of a 'configure' invocation, assuming a Bourne-like
|
||||
shell such as Bash, which uses these variables:
|
||||
|
||||
./configure \
|
||||
CPPFLAGS='-I/foo/myinclude' LDFLAGS='-L/bar/mylib' \
|
||||
CFLAGS='-O3' LIBS='-lfoo -lbar'
|
||||
|
||||
(this is all one shell command). This tells `configure' to instruct the
|
||||
preprocessor to look in the `/foo/myinclude' directory for header
|
||||
(this is all one shell command). This tells 'configure' to instruct the
|
||||
preprocessor to look in the '/foo/myinclude' directory for header
|
||||
files (in addition to the standard directories), instruct the linker
|
||||
to look in `/bar/mylib' for libraries, pass the -O3 optimization
|
||||
to look in '/bar/mylib' for libraries, pass the -O3 optimization
|
||||
switch to the compiler, and link against libfoo and libbar
|
||||
libraries in addition to the standard ones.
|
||||
|
||||
For some libraries, like Gtk+, fontconfig and ALSA, `configure' uses
|
||||
For some libraries, like Gtk+, fontconfig and ALSA, 'configure' uses
|
||||
pkg-config to find where those libraries are installed.
|
||||
If you want pkg-config to look in special directories, you have to set
|
||||
PKG_CONFIG_PATH to point to the directories where the .pc-files for
|
||||
@ -417,27 +417,27 @@ those libraries are. For example:
|
||||
PKG_CONFIG_PATH='/usr/local/alsa/lib/pkgconfig:/opt/gtk+-2.8/lib/pkgconfig'
|
||||
|
||||
3b) To build in a separate directory, go to that directory
|
||||
and run the program `configure' as follows:
|
||||
and run the program 'configure' as follows:
|
||||
|
||||
SOURCE-DIR/configure CONFIGURATION-NAME [--OPTION[=VALUE]] ...
|
||||
|
||||
SOURCE-DIR refers to the top-level Emacs source directory which is
|
||||
where Emacs's configure script is located. `configure' looks for the
|
||||
Emacs source code in the directory that `configure' is in.
|
||||
where Emacs's configure script is located. 'configure' looks for the
|
||||
Emacs source code in the directory that 'configure' is in.
|
||||
|
||||
4) Put into `./lisp/site-init.el' or `./lisp/site-load.el' any Emacs
|
||||
4) Put into './lisp/site-init.el' or './lisp/site-load.el' any Emacs
|
||||
Lisp code you want Emacs to load before it is dumped out. Use
|
||||
site-load.el for additional libraries if you arrange for their
|
||||
documentation strings to be in the etc/DOC file (see
|
||||
src/Makefile.in if you wish to figure out how to do that). For all
|
||||
else, use site-init.el. Do not load byte-compiled code which
|
||||
was built with a non-nil value of `byte-compile-dynamic'.
|
||||
was built with a non-nil value of 'byte-compile-dynamic'.
|
||||
|
||||
It is not a good idea to edit the normal .el files that come with Emacs.
|
||||
Instead, use a file like site-init.el to change settings.
|
||||
|
||||
To change the value of a variable that is already defined in Emacs,
|
||||
you should use the Lisp function `setq', not `defvar'. For example,
|
||||
you should use the Lisp function 'setq', not 'defvar'. For example,
|
||||
|
||||
(setq news-inews-program "/usr/bin/inews")
|
||||
|
||||
@ -449,46 +449,46 @@ variable gets by default! Make sure you know what kind of value the
|
||||
variable should have. If you don't pay attention to what you are
|
||||
doing, you'll make a mistake.
|
||||
|
||||
The `site-*.el' files are nonexistent in the distribution. You do not
|
||||
The 'site-*.el' files are nonexistent in the distribution. You do not
|
||||
need to create them if you have nothing to put in them.
|
||||
|
||||
5) Refer to the file `./etc/TERMS' for information on fields you may
|
||||
5) Refer to the file './etc/TERMS' for information on fields you may
|
||||
wish to add to various termcap entries. (This is unlikely to be necessary.)
|
||||
|
||||
6) Run `make' in the top directory of the Emacs distribution to finish
|
||||
6) Run 'make' in the top directory of the Emacs distribution to finish
|
||||
building Emacs in the standard way. The final executable file is
|
||||
named `src/emacs'. You can execute this file "in place" without
|
||||
named 'src/emacs'. You can execute this file "in place" without
|
||||
copying it, if you wish; then it automatically uses the sibling
|
||||
directories ../lisp, ../lib-src, ../info.
|
||||
|
||||
Or you can "install" the executable and the other files into their
|
||||
installed locations, with `make install'. By default, Emacs's files
|
||||
installed locations, with 'make install'. By default, Emacs's files
|
||||
are installed in the following directories:
|
||||
|
||||
`/usr/local/bin' holds the executable programs users normally run -
|
||||
`emacs', `etags', `ctags', `emacsclient'.
|
||||
'/usr/local/bin' holds the executable programs users normally run -
|
||||
'emacs', 'etags', 'ctags', 'emacsclient'.
|
||||
|
||||
`/usr/local/share/emacs/VERSION/lisp' holds the Emacs Lisp library;
|
||||
`VERSION' stands for the number of the Emacs version
|
||||
you are installing, like `23.1' or `23.2'. Since the
|
||||
'/usr/local/share/emacs/VERSION/lisp' holds the Emacs Lisp library;
|
||||
'VERSION' stands for the number of the Emacs version
|
||||
you are installing, like '23.1' or '23.2'. Since the
|
||||
Lisp library changes from one version of Emacs to
|
||||
another, including the version number in the path
|
||||
allows you to have several versions of Emacs installed
|
||||
at the same time; in particular, you don't have to
|
||||
make Emacs unavailable while installing a new version.
|
||||
|
||||
`/usr/local/share/emacs/VERSION/etc' holds the Emacs tutorial, the DOC
|
||||
'/usr/local/share/emacs/VERSION/etc' holds the Emacs tutorial, the DOC
|
||||
file, and other architecture-independent files Emacs
|
||||
might need while running.
|
||||
|
||||
`/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' contains executable
|
||||
'/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME' contains executable
|
||||
programs used by Emacs that users are not expected to
|
||||
run themselves.
|
||||
`VERSION' is the number of the Emacs version you are
|
||||
installing, and `CONFIGURATION-NAME' is the value
|
||||
deduced by the `configure' program to identify the
|
||||
'VERSION' is the number of the Emacs version you are
|
||||
installing, and 'CONFIGURATION-NAME' is the value
|
||||
deduced by the 'configure' program to identify the
|
||||
architecture and operating system of your machine,
|
||||
like `i686-pc-linux-gnu' or `sparc-sun-sunos'. Since
|
||||
like 'i686-pc-linux-gnu' or 'sparc-sun-sunos'. Since
|
||||
these files are specific to the version of Emacs,
|
||||
operating system, and architecture in use, including
|
||||
the configuration name in the path allows you to have
|
||||
@ -497,35 +497,35 @@ are installed in the following directories:
|
||||
useful for sites at which different kinds of machines
|
||||
share the file system Emacs is installed on.
|
||||
|
||||
`/usr/local/share/info' holds the on-line documentation for Emacs,
|
||||
'/usr/local/share/info' holds the on-line documentation for Emacs,
|
||||
known as "info files". Many other GNU programs are
|
||||
documented using info files as well, so this directory
|
||||
stands apart from the other, Emacs-specific directories.
|
||||
|
||||
`/usr/local/share/man/man1' holds the man pages for the programs installed
|
||||
in `/usr/local/bin'.
|
||||
'/usr/local/share/man/man1' holds the man pages for the programs installed
|
||||
in '/usr/local/bin'.
|
||||
|
||||
Any version of Emacs, whether installed or not, also looks for Lisp
|
||||
files in these directories.
|
||||
|
||||
`/usr/local/share/emacs/VERSION/site-lisp' holds the local Emacs Lisp
|
||||
'/usr/local/share/emacs/VERSION/site-lisp' holds the local Emacs Lisp
|
||||
files installed for Emacs version VERSION only.
|
||||
|
||||
`/usr/local/share/emacs/site-lisp' holds the local Emacs Lisp
|
||||
'/usr/local/share/emacs/site-lisp' holds the local Emacs Lisp
|
||||
files installed for all Emacs versions.
|
||||
|
||||
When Emacs is installed, it searches for its Lisp files
|
||||
in `/usr/local/share/emacs/VERSION/site-lisp', then in
|
||||
`/usr/local/share/emacs/site-lisp', and finally in
|
||||
`/usr/local/share/emacs/VERSION/lisp'.
|
||||
in '/usr/local/share/emacs/VERSION/site-lisp', then in
|
||||
'/usr/local/share/emacs/site-lisp', and finally in
|
||||
'/usr/local/share/emacs/VERSION/lisp'.
|
||||
|
||||
If these directories are not what you want, you can specify where to
|
||||
install Emacs's libraries and data files or where Emacs should search
|
||||
for its Lisp files by giving values for `make' variables as part of
|
||||
the command. See the section below called `MAKE VARIABLES' for more
|
||||
for its Lisp files by giving values for 'make' variables as part of
|
||||
the command. See the section below called 'MAKE VARIABLES' for more
|
||||
information on this.
|
||||
|
||||
7) Check the file `dir' in your site's info directory (usually
|
||||
7) Check the file 'dir' in your site's info directory (usually
|
||||
/usr/local/share/info) to make sure that it has a menu entry for the
|
||||
Emacs info files.
|
||||
|
||||
@ -534,51 +534,51 @@ then you might need to make the movemail program setuid or setgid
|
||||
to enable it to write the lock files. We believe this is safe.
|
||||
|
||||
9) You are done! You can remove executables and object files from
|
||||
the build directory by typing `make clean'. To also remove the files
|
||||
that `configure' created (so you can compile Emacs for a different
|
||||
configuration), type `make distclean'.
|
||||
the build directory by typing 'make clean'. To also remove the files
|
||||
that 'configure' created (so you can compile Emacs for a different
|
||||
configuration), type 'make distclean'.
|
||||
|
||||
|
||||
MAKE VARIABLES
|
||||
|
||||
You can change where the build process installs Emacs and its data
|
||||
files by specifying values for `make' variables as part of the `make'
|
||||
files by specifying values for 'make' variables as part of the 'make'
|
||||
command line. For example, if you type
|
||||
|
||||
make install bindir=/usr/local/gnubin
|
||||
|
||||
the `bindir=/usr/local/gnubin' argument indicates that the Emacs
|
||||
executable files should go in `/usr/local/gnubin', not
|
||||
`/usr/local/bin'.
|
||||
the 'bindir=/usr/local/gnubin' argument indicates that the Emacs
|
||||
executable files should go in '/usr/local/gnubin', not
|
||||
'/usr/local/bin'.
|
||||
|
||||
Here is a complete list of the variables you may want to set.
|
||||
|
||||
`bindir' indicates where to put executable programs that users can
|
||||
'bindir' indicates where to put executable programs that users can
|
||||
run. This defaults to /usr/local/bin.
|
||||
|
||||
`datadir' indicates where to put the architecture-independent
|
||||
'datadir' indicates where to put the architecture-independent
|
||||
read-only data files that Emacs refers to while it runs; it
|
||||
defaults to /usr/local/share. We create the following
|
||||
subdirectories under `datadir':
|
||||
- `emacs/VERSION/lisp', containing the Emacs Lisp library, and
|
||||
- `emacs/VERSION/etc', containing the tutorials, DOC file, etc.
|
||||
`VERSION' is the number of the Emacs version you are installing,
|
||||
like `23.1' or `23.2'. Since these files vary from one version
|
||||
subdirectories under 'datadir':
|
||||
- 'emacs/VERSION/lisp', containing the Emacs Lisp library, and
|
||||
- 'emacs/VERSION/etc', containing the tutorials, DOC file, etc.
|
||||
'VERSION' is the number of the Emacs version you are installing,
|
||||
like '23.1' or '23.2'. Since these files vary from one version
|
||||
of Emacs to another, including the version number in the path
|
||||
allows you to have several versions of Emacs installed at the
|
||||
same time; this means that you don't have to make Emacs
|
||||
unavailable while installing a new version.
|
||||
|
||||
`libexecdir' indicates where to put architecture-specific data files that
|
||||
Emacs refers to as it runs; it defaults to `/usr/local/libexec'.
|
||||
We create the following subdirectories under `libexecdir':
|
||||
- `emacs/VERSION/CONFIGURATION-NAME', containing executable
|
||||
'libexecdir' indicates where to put architecture-specific data files that
|
||||
Emacs refers to as it runs; it defaults to '/usr/local/libexec'.
|
||||
We create the following subdirectories under 'libexecdir':
|
||||
- 'emacs/VERSION/CONFIGURATION-NAME', containing executable
|
||||
programs used by Emacs that users are not expected to run
|
||||
themselves.
|
||||
`VERSION' is the number of the Emacs version you are installing,
|
||||
and `CONFIGURATION-NAME' is the value deduced by the
|
||||
`configure' program to identify the architecture and operating
|
||||
system of your machine, like `i686-pc-linux-gnu' or `sparc-sun-sunos'.
|
||||
'VERSION' is the number of the Emacs version you are installing,
|
||||
and 'CONFIGURATION-NAME' is the value deduced by the
|
||||
'configure' program to identify the architecture and operating
|
||||
system of your machine, like 'i686-pc-linux-gnu' or 'sparc-sun-sunos'.
|
||||
Since these files are specific to the version of Emacs,
|
||||
operating system, and architecture in use, including the
|
||||
configuration name in the path allows you to have several
|
||||
@ -587,57 +587,57 @@ Here is a complete list of the variables you may want to set.
|
||||
at which different kinds of machines share the file system
|
||||
Emacs is installed on.
|
||||
|
||||
`infodir' indicates where to put the info files distributed with
|
||||
Emacs; it defaults to `/usr/local/share/info'.
|
||||
'infodir' indicates where to put the info files distributed with
|
||||
Emacs; it defaults to '/usr/local/share/info'.
|
||||
|
||||
`mandir' indicates where to put the man pages for Emacs and its
|
||||
utilities (like `etags'); it defaults to
|
||||
`/usr/local/share/man/man1'.
|
||||
'mandir' indicates where to put the man pages for Emacs and its
|
||||
utilities (like 'etags'); it defaults to
|
||||
'/usr/local/share/man/man1'.
|
||||
|
||||
`prefix' doesn't give a path for any specific part of Emacs; instead,
|
||||
'prefix' doesn't give a path for any specific part of Emacs; instead,
|
||||
its value is used to determine the defaults for all the
|
||||
architecture-independent path variables - `datadir',
|
||||
`sharedstatedir', `infodir', and `mandir'. Its default value is
|
||||
`/usr/local'; the other variables add on `lib' or `man' to it
|
||||
architecture-independent path variables - 'datadir',
|
||||
'sharedstatedir', 'infodir', and 'mandir'. Its default value is
|
||||
'/usr/local'; the other variables add on 'lib' or 'man' to it
|
||||
by default.
|
||||
|
||||
For example, suppose your site generally places GNU software
|
||||
under `/usr/users/software/gnusoft' instead of `/usr/local'.
|
||||
under '/usr/users/software/gnusoft' instead of '/usr/local'.
|
||||
By including
|
||||
`prefix=/usr/users/software/gnusoft'
|
||||
in the arguments to `make', you can instruct the build process
|
||||
'prefix=/usr/users/software/gnusoft'
|
||||
in the arguments to 'make', you can instruct the build process
|
||||
to place all of the Emacs data files in the appropriate
|
||||
directories under that path.
|
||||
|
||||
`exec_prefix' serves the same purpose as `prefix', but instead
|
||||
'exec_prefix' serves the same purpose as 'prefix', but instead
|
||||
determines the default values for the architecture-dependent
|
||||
path variables - `bindir' and `libexecdir'.
|
||||
path variables - 'bindir' and 'libexecdir'.
|
||||
|
||||
The above variables serve analogous purposes in the makefiles for all
|
||||
GNU software; the following variables are specific to Emacs.
|
||||
|
||||
`archlibdir' indicates where Emacs installs and expects the executable
|
||||
'archlibdir' indicates where Emacs installs and expects the executable
|
||||
files and other architecture-dependent data it uses while
|
||||
running. Its default value, based on `libexecdir' (which
|
||||
see), is `/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME'
|
||||
running. Its default value, based on 'libexecdir' (which
|
||||
see), is '/usr/local/libexec/emacs/VERSION/CONFIGURATION-NAME'
|
||||
(where VERSION and CONFIGURATION-NAME are as described above).
|
||||
|
||||
`GZIP_PROG' is the name of the executable that compresses installed info,
|
||||
'GZIP_PROG' is the name of the executable that compresses installed info,
|
||||
manual, and .el files. It defaults to gzip. Setting it to
|
||||
the empty string suppresses compression.
|
||||
|
||||
Remember that you must specify any variable values you need each time
|
||||
you run `make' in the top directory. If you run `make' once to build
|
||||
emacs, test it, and then run `make' again to install the files, you
|
||||
you run 'make' in the top directory. If you run 'make' once to build
|
||||
emacs, test it, and then run 'make' again to install the files, you
|
||||
must provide the same variable settings each time. To make the
|
||||
settings persist, you can edit them into the `Makefile' in the top
|
||||
directory, but be aware that running the `configure' program erases
|
||||
`Makefile' and rebuilds it from `Makefile.in'.
|
||||
settings persist, you can edit them into the 'Makefile' in the top
|
||||
directory, but be aware that running the 'configure' program erases
|
||||
'Makefile' and rebuilds it from 'Makefile.in'.
|
||||
|
||||
The path for finding Lisp files is specified in src/epaths.h,
|
||||
a file which is generated by running configure. To change the path,
|
||||
you can edit the definition of PATH_LOADSEARCH in that file
|
||||
before you run `make'.
|
||||
before you run 'make'.
|
||||
|
||||
The top-level Makefile stores the variable settings it used in the
|
||||
Makefiles for the subdirectories, so you don't have to specify them
|
||||
@ -646,7 +646,7 @@ when running make in the subdirectories.
|
||||
|
||||
PROBLEMS
|
||||
|
||||
See the file `./etc/PROBLEMS' for a list of various problems sometimes
|
||||
See the file './etc/PROBLEMS' for a list of various problems sometimes
|
||||
encountered, and what to do about them.
|
||||
|
||||
This file is part of GNU Emacs.
|
||||
|
||||
58
Makefile.in
58
Makefile.in
@ -30,13 +30,13 @@
|
||||
# by building, but normally aren't because the distribution comes
|
||||
# with them.
|
||||
#
|
||||
# Delete `.dvi' files here if they are not part of the distribution.
|
||||
# Delete '.dvi' files here if they are not part of the distribution.
|
||||
#
|
||||
# make distclean
|
||||
# Delete all files from the current directory that are created by
|
||||
# configuring or building the program. If you have unpacked the
|
||||
# source and built the program without creating any other files,
|
||||
# `make distclean' should leave only the files that were in the
|
||||
# 'make distclean' should leave only the files that were in the
|
||||
# distribution.
|
||||
#
|
||||
# make maintainer-clean
|
||||
@ -67,7 +67,7 @@ CDPATH=
|
||||
# If Make doesn't predefine MAKE, set it here.
|
||||
@SET_MAKE@
|
||||
|
||||
# ==================== Things `configure' Might Edit ====================
|
||||
# ==================== Things 'configure' Might Edit ====================
|
||||
|
||||
cache_file = @cache_file@
|
||||
CONFIGURE_FLAGS = --cache-file=$(cache_file)
|
||||
@ -84,11 +84,11 @@ EXEEXT=@EXEEXT@
|
||||
### to install files in.
|
||||
|
||||
### This should be the number of the Emacs version we're building,
|
||||
### like `18.59' or `19.0'.
|
||||
### like '24.5' or '25.0.50'.
|
||||
version=@version@
|
||||
|
||||
### This should be the name of the configuration we're building Emacs
|
||||
### for, like `mips-dec-ultrix' or `sparc-sun-sunos'.
|
||||
### for, like 'x86_64-unknown-linux-gnu' or 'powerpc-ibm-aix7.1.2.0'.
|
||||
configuration=@configuration@
|
||||
|
||||
### The nt/ subdirectory gets built only for MinGW
|
||||
@ -122,7 +122,7 @@ ns_self_contained=@ns_self_contained@
|
||||
# not need to change them. This defaults to /usr/local.
|
||||
prefix=@prefix@
|
||||
|
||||
# Like `prefix', but used for architecture-specific files.
|
||||
# Like 'prefix', but used for architecture-specific files.
|
||||
exec_prefix=@exec_prefix@
|
||||
|
||||
# Where to install Emacs and other binaries that people will want to
|
||||
@ -171,7 +171,7 @@ bitmapdir=@bitmapdir@
|
||||
# Where to find the source code. The source code for Emacs's C kernel is
|
||||
# expected to be in ${srcdir}/src, and the source code for Emacs's
|
||||
# utility programs is expected to be in ${srcdir}/lib-src. This is
|
||||
# set by the configure script's `--srcdir' option.
|
||||
# set by the configure script's '--srcdir' option.
|
||||
|
||||
# We use $(srcdir) explicitly in dependencies so as not to depend on VPATH.
|
||||
srcdir=@srcdir@
|
||||
@ -316,7 +316,7 @@ etc-emacsver:
|
||||
|
||||
removenullpaths=sed -e 's/^:*//' -e 's/:*$$//g' -e 's/::*/:/g'
|
||||
|
||||
# Generate epaths.h from epaths.in. This target is invoked by `configure'.
|
||||
# Generate epaths.h from epaths.in. This target is invoked by 'configure'.
|
||||
# See comments in configure.ac for why it is done this way, as opposed
|
||||
# to just letting configure generate epaths.h from epaths.in in a
|
||||
# similar way to how Makefile is made from Makefile.in.
|
||||
@ -350,7 +350,7 @@ epaths-force:
|
||||
# The w32 build needs a slightly different editing, and it uses
|
||||
# nt/epaths.nt as the template.
|
||||
#
|
||||
# Use the value of ${locallisppath} supplied by `configure',
|
||||
# Use the value of ${locallisppath} supplied by 'configure',
|
||||
# to support the --enable-locallisppath argument.
|
||||
#
|
||||
# In this case, the paths written to 'src/epaths.h' must be in native
|
||||
@ -377,10 +377,10 @@ lib-src src: $(NTDIR) lib
|
||||
|
||||
src: lib-src
|
||||
|
||||
# We need to build `emacs' in `src' to compile the *.elc files in `lisp'.
|
||||
# We need to build 'emacs' in 'src' to compile the *.elc files in 'lisp'.
|
||||
lisp: src
|
||||
|
||||
# These targets should be "${SUBDIR} without `src'".
|
||||
# These targets should be "${SUBDIR} without 'src'".
|
||||
lib lib-src lisp nt: Makefile
|
||||
$(MAKE) -C $@ all
|
||||
|
||||
@ -733,8 +733,8 @@ install-etc:
|
||||
install-strip:
|
||||
$(MAKE) INSTALL_STRIP=-s install
|
||||
|
||||
### Delete all the installed files that the `install' target would
|
||||
### create (but not the noninstalled files such as `make all' would create).
|
||||
### Delete all the installed files that the 'install' target would
|
||||
### create (but not the noninstalled files such as 'make all' would create).
|
||||
###
|
||||
### Don't delete the lisp and etc directories if they're in the source tree.
|
||||
uninstall: uninstall-$(NTDIR) uninstall-doc
|
||||
@ -803,10 +803,10 @@ $(1)_$(2):
|
||||
$$(MAKE) -C $(1) $(2)
|
||||
endef
|
||||
|
||||
### `mostlyclean'
|
||||
### Like `clean', but may refrain from deleting a few files that people
|
||||
### normally don't want to recompile. For example, the `mostlyclean'
|
||||
### target for GCC does not delete `libgcc.a', because recompiling it
|
||||
### 'mostlyclean'
|
||||
### Like 'clean', but may refrain from deleting a few files that people
|
||||
### normally don't want to recompile. For example, the 'mostlyclean'
|
||||
### target for GCC does not delete 'libgcc.a', because recompiling it
|
||||
### is rarely necessary and takes a lot of time.
|
||||
mostlyclean_dirs = src oldXMenu lwlib lib lib-src nt doc/emacs doc/misc \
|
||||
doc/lispref doc/lispintro
|
||||
@ -818,14 +818,14 @@ mostlyclean: $(mostlyclean_dirs:=_mostlyclean)
|
||||
[ ! -d $$dir ] || $(MAKE) -C $$dir mostlyclean; \
|
||||
done
|
||||
|
||||
### `clean'
|
||||
### 'clean'
|
||||
### Delete all files from the current directory that are normally
|
||||
### created by building the program. Don't delete the files that
|
||||
### record the configuration. Also preserve files that could be made
|
||||
### by building, but normally aren't because the distribution comes
|
||||
### with them.
|
||||
###
|
||||
### Delete `.dvi' files here if they are not part of the distribution.
|
||||
### Delete '.dvi' files here if they are not part of the distribution.
|
||||
clean_dirs = $(mostlyclean_dirs) nextstep
|
||||
|
||||
$(foreach dir,$(clean_dirs),$(eval $(call submake_template,$(dir),clean)))
|
||||
@ -837,16 +837,16 @@ clean: $(clean_dirs:=_clean)
|
||||
-rm -f *.tmp etc/*.tmp*
|
||||
-rm -rf info-dir.*
|
||||
|
||||
### `bootclean'
|
||||
### 'bootclean'
|
||||
### Delete all files that need to be remade for a clean bootstrap.
|
||||
top_bootclean=\
|
||||
rm -f config.cache config.log ${srcdir}/doc/man/emacs.1
|
||||
|
||||
### `distclean'
|
||||
### 'distclean'
|
||||
### Delete all files from the current directory that are created by
|
||||
### configuring or building the program. If you have unpacked the
|
||||
### source and built the program without creating any other files,
|
||||
### `make distclean' should leave only the files that were in the
|
||||
### 'make distclean' should leave only the files that were in the
|
||||
### distribution.
|
||||
top_distclean=\
|
||||
${top_bootclean}; \
|
||||
@ -862,8 +862,8 @@ distclean: $(distclean_dirs:=_distclean)
|
||||
done
|
||||
${top_distclean}
|
||||
|
||||
### `bootstrap-clean'
|
||||
### Delete everything that can be reconstructed by `make' and that
|
||||
### 'bootstrap-clean'
|
||||
### Delete everything that can be reconstructed by 'make' and that
|
||||
### needs to be deleted in order to force a bootstrap from a clean state.
|
||||
$(foreach dir,$(distclean_dirs),$(eval $(call submake_template,$(dir),bootstrap-clean)))
|
||||
|
||||
@ -876,16 +876,16 @@ bootstrap-clean: $(distclean_dirs:=_bootstrap-clean)
|
||||
rm -f ${srcdir}/etc/refcards/emacsver.tex
|
||||
${top_bootclean}
|
||||
|
||||
### `maintainer-clean'
|
||||
### 'maintainer-clean'
|
||||
### Delete everything from the current directory that can be
|
||||
### reconstructed with this Makefile. This typically includes
|
||||
### everything deleted by distclean, plus more: C source files
|
||||
### produced by Bison, tags tables, info files, and so on.
|
||||
###
|
||||
### One exception, however: `make maintainer-clean' should not delete
|
||||
### `configure' even if `configure' can be remade using a rule in the
|
||||
### Makefile. More generally, `make maintainer-clean' should not delete
|
||||
### anything that needs to exist in order to run `configure' and then
|
||||
### One exception, however: 'make maintainer-clean' should not delete
|
||||
### 'configure' even if 'configure' can be remade using a rule in the
|
||||
### Makefile. More generally, 'make maintainer-clean' should not delete
|
||||
### anything that needs to exist in order to run 'configure' and then
|
||||
### begin to build the program.
|
||||
top_maintainer_clean=\
|
||||
${top_distclean}; \
|
||||
|
||||
56
README
56
README
@ -22,71 +22,71 @@ in code we don't use often. Please send bug reports to the mailing
|
||||
list bug-gnu-emacs@gnu.org. If possible, use M-x report-emacs-bug.
|
||||
|
||||
See the "Bugs" section of the Emacs manual for more information on how
|
||||
to report bugs. (The file `BUGS' in this directory explains how you
|
||||
to report bugs. (The file 'BUGS' in this directory explains how you
|
||||
can find and read that section using the Info files that come with
|
||||
Emacs.) For a list of mailing lists related to Emacs, see
|
||||
<http://savannah.gnu.org/mail/?group=emacs>. For the complete
|
||||
list of GNU mailing lists, see <http://lists.gnu.org/>.
|
||||
|
||||
The `etc' subdirectory contains several other files, named in capital
|
||||
The 'etc' subdirectory contains several other files, named in capital
|
||||
letters, which you might consider looking at when installing GNU
|
||||
Emacs.
|
||||
|
||||
The file `configure' is a shell script to acclimate Emacs to the
|
||||
The file 'configure' is a shell script to acclimate Emacs to the
|
||||
oddities of your processor and operating system. It creates the file
|
||||
`Makefile' (a script for the `make' program), which automates the
|
||||
'Makefile' (a script for the 'make' program), which automates the
|
||||
process of building and installing Emacs. See INSTALL for more
|
||||
detailed information.
|
||||
|
||||
The file `configure.ac' is the input used by the autoconf program to
|
||||
construct the `configure' script.
|
||||
The file 'configure.ac' is the input used by the autoconf program to
|
||||
construct the 'configure' script.
|
||||
|
||||
The shell script `autogen.sh' generates 'configure' and other files by
|
||||
The shell script 'autogen.sh' generates 'configure' and other files by
|
||||
running the GNU build tools autoconf and automake, which in turn use
|
||||
GNU m4 and Perl. If you want to use it, you will need to install
|
||||
recent versions of these build tools. This should be needed only if
|
||||
you edit files like `configure.ac' that specify Emacs's autobuild
|
||||
you edit files like 'configure.ac' that specify Emacs's autobuild
|
||||
procedure.
|
||||
|
||||
The file `Makefile.in' is a template used by `configure' to create
|
||||
`Makefile'.
|
||||
The file 'Makefile.in' is a template used by 'configure' to create
|
||||
'Makefile'.
|
||||
|
||||
The file `make-dist' is a shell script to build a distribution tar
|
||||
The file 'make-dist' is a shell script to build a distribution tar
|
||||
file from the current Emacs tree, containing only those files
|
||||
appropriate for distribution. If you make extensive changes to Emacs,
|
||||
this script will help you distribute your version to others.
|
||||
|
||||
There are several subdirectories:
|
||||
|
||||
`src' holds the C code for Emacs (the Emacs Lisp interpreter and
|
||||
'src' holds the C code for Emacs (the Emacs Lisp interpreter and
|
||||
its primitives, the redisplay code, and some basic editing
|
||||
functions).
|
||||
`lisp' holds the Emacs Lisp code for Emacs (most everything else).
|
||||
`leim' holds the original source files for the generated files
|
||||
'lisp' holds the Emacs Lisp code for Emacs (most everything else).
|
||||
'leim' holds the original source files for the generated files
|
||||
in lisp/leim. These form the library of Emacs input methods,
|
||||
required to type international characters that can't be
|
||||
directly produced by your keyboard.
|
||||
`lib' holds source code for libraries used by Emacs and its utilities
|
||||
`lib-src' holds the source code for some utility programs for use by or
|
||||
'lib' holds source code for libraries used by Emacs and its utilities
|
||||
'lib-src' holds the source code for some utility programs for use by or
|
||||
with Emacs, like movemail and etags.
|
||||
`etc' holds miscellaneous architecture-independent data files Emacs
|
||||
'etc' holds miscellaneous architecture-independent data files Emacs
|
||||
uses, like the tutorial text and tool bar images.
|
||||
The contents of the `lisp', `leim', `info', and `doc'
|
||||
The contents of the 'lisp', 'leim', 'info', and 'doc'
|
||||
subdirectories are architecture-independent too.
|
||||
`info' holds the Info documentation tree for Emacs.
|
||||
`doc/emacs' holds the source code for the Emacs Manual. If you modify the
|
||||
manual sources, you will need the `makeinfo' program to produce
|
||||
an updated manual. `makeinfo' is part of the GNU Texinfo
|
||||
'info' holds the Info documentation tree for Emacs.
|
||||
'doc/emacs' holds the source code for the Emacs Manual. If you modify the
|
||||
manual sources, you will need the 'makeinfo' program to produce
|
||||
an updated manual. 'makeinfo' is part of the GNU Texinfo
|
||||
package; you need a suitably recent version of Texinfo.
|
||||
`doc/lispref' holds the source code for the Emacs Lisp reference manual.
|
||||
`doc/lispintro' holds the source code for the Introduction to Programming
|
||||
'doc/lispref' holds the source code for the Emacs Lisp reference manual.
|
||||
'doc/lispintro' holds the source code for the Introduction to Programming
|
||||
in Emacs Lisp manual.
|
||||
`msdos' holds configuration files for compiling Emacs under MS-DOS.
|
||||
`nextstep' holds instructions and some other files for compiling the
|
||||
'msdos' holds configuration files for compiling Emacs under MS-DOS.
|
||||
'nextstep' holds instructions and some other files for compiling the
|
||||
Nextstep port of Emacs, for GNUstep and Mac OS X Cocoa.
|
||||
`nt' holds various command files and documentation files that pertain
|
||||
'nt' holds various command files and documentation files that pertain
|
||||
to building and running Emacs on Windows 9X/ME/NT/2000/XP.
|
||||
`test' holds tests for various aspects of Emacs's functionality.
|
||||
'test' holds tests for various aspects of Emacs's functionality.
|
||||
|
||||
Building Emacs on non-Posix platforms requires tools that aren't part
|
||||
of the standard distribution of the OS. The platform-specific README
|
||||
|
||||
150
configure.ac
150
configure.ac
@ -1,6 +1,6 @@
|
||||
dnl Autoconf script for GNU Emacs
|
||||
dnl To rebuild the `configure' script from this, execute the command
|
||||
dnl autoconf
|
||||
dnl To rebuild the 'configure' script from this, execute the command
|
||||
dnl autoconf
|
||||
dnl in the directory containing this script.
|
||||
dnl If you changed any AC_DEFINES, also run autoheader.
|
||||
dnl
|
||||
@ -283,8 +283,8 @@ AC_ARG_WITH([sound],[AS_HELP_STRING([--with-sound=VALUE],
|
||||
default yes). Only for GNU/Linux, FreeBSD, NetBSD, MinGW, Cygwin.])],
|
||||
[ case "${withval}" in
|
||||
yes|no|alsa|oss|bsd-ossaudio) val=$withval ;;
|
||||
*) AC_MSG_ERROR([`--with-sound=$withval' is invalid;
|
||||
this option's value should be `yes', `no', `alsa', `oss', or `bsd-ossaudio'.])
|
||||
*) AC_MSG_ERROR(['--with-sound=$withval' is invalid;
|
||||
this option's value should be 'yes', 'no', 'alsa', 'oss', or 'bsd-ossaudio'.])
|
||||
;;
|
||||
esac
|
||||
with_sound=$val
|
||||
@ -307,10 +307,10 @@ AC_ARG_WITH([x-toolkit],[AS_HELP_STRING([--with-x-toolkit=KIT],
|
||||
gtk2 ) val=gtk2 ;;
|
||||
gtk3 ) val=gtk3 ;;
|
||||
* )
|
||||
AC_MSG_ERROR([`--with-x-toolkit=$withval' is invalid;
|
||||
this option's value should be `yes', `no', `lucid', `athena', `motif', `gtk',
|
||||
`gtk2' or `gtk3'. `yes' and `gtk' are synonyms.
|
||||
`athena' and `lucid' are synonyms.])
|
||||
AC_MSG_ERROR(['--with-x-toolkit=$withval' is invalid;
|
||||
this option's value should be 'yes', 'no', 'lucid', 'athena', 'motif', 'gtk',
|
||||
'gtk2' or 'gtk3'. 'yes' and 'gtk' are synonyms.
|
||||
'athena' and 'lucid' are synonyms.])
|
||||
;;
|
||||
esac
|
||||
with_x_toolkit=$val
|
||||
@ -359,10 +359,10 @@ AC_ARG_WITH([file-notification],[AS_HELP_STRING([--with-file-notification=LIB],
|
||||
g | gf | gfi | gfil | gfile ) val=gfile ;;
|
||||
i | in | ino | inot | inoti | inotif | inotify ) val=inotify ;;
|
||||
w | w3 | w32 ) val=w32 ;;
|
||||
* ) AC_MSG_ERROR([`--with-file-notification=$withval' is invalid;
|
||||
this option's value should be `yes', `no', `gfile', `inotify' or `w32'.
|
||||
`yes' is a synonym for `w32' on MS-Windows, for `no' on Nextstep,
|
||||
otherwise for the first of `gfile' or `inotify' that is usable.])
|
||||
* ) AC_MSG_ERROR(['--with-file-notification=$withval' is invalid;
|
||||
this option's value should be 'yes', 'no', 'gfile', 'inotify' or 'w32'.
|
||||
'yes' is a synonym for 'w32' on MS-Windows, for 'no' on Nextstep,
|
||||
otherwise for the first of 'gfile' or 'inotify' that is usable.])
|
||||
;;
|
||||
esac
|
||||
with_file_notification=$val
|
||||
@ -458,8 +458,8 @@ do
|
||||
ac_gc_check_cons_list=1 ;
|
||||
ac_glyphs_debug=1 ;;
|
||||
# these enable particular checks
|
||||
stringbytes) ac_gc_check_stringbytes=1 ;;
|
||||
stringoverrun) ac_gc_check_string_overrun=1 ;;
|
||||
stringbytes) ac_gc_check_stringbytes=1 ;;
|
||||
stringoverrun) ac_gc_check_string_overrun=1 ;;
|
||||
stringfreelist) ac_gc_check_string_free_list=1 ;;
|
||||
xmallocoverrun) ac_xmalloc_overrun=1 ;;
|
||||
conslist) ac_gc_check_cons_list=1 ;;
|
||||
@ -530,7 +530,7 @@ AC_SUBST(PROFILING_CFLAGS)
|
||||
AC_ARG_ENABLE(autodepend,
|
||||
[AS_HELP_STRING([--enable-autodepend],
|
||||
[automatically generate dependencies to .h-files.
|
||||
Requires gcc, enabled if found.])],
|
||||
Requires gcc, enabled if found.])],
|
||||
[ac_enable_autodepend="${enableval}"],[ac_enable_autodepend=yes])
|
||||
|
||||
AC_ARG_ENABLE(gtk-deprecation-warnings,
|
||||
@ -538,7 +538,7 @@ AC_ARG_ENABLE(gtk-deprecation-warnings,
|
||||
[Show Gtk+/Gdk deprecation warnings for Gtk+ >= 3.0])],
|
||||
[ac_enable_gtk_deprecation_warnings="${enableval}"],[])
|
||||
|
||||
dnl This used to use changequote, but, apart from `changequote is evil'
|
||||
dnl This used to use changequote, but, apart from 'changequote is evil'
|
||||
dnl per the autoconf manual, we can speed up autoconf somewhat by quoting
|
||||
dnl the great gob of text. Thus it's not processed for possible expansion.
|
||||
dnl Just make sure the brackets remain balanced.
|
||||
@ -645,7 +645,7 @@ case "${canonical}" in
|
||||
mips-sgi-irix6.5 )
|
||||
opsys=irix6-5
|
||||
# Without defining _LANGUAGE_C, things get masked out in the headers
|
||||
# so that, for instance, grepping for `free' in stdlib.h fails and
|
||||
# so that, for instance, grepping for 'free' in stdlib.h fails and
|
||||
# AC_HEADER_STD_C fails. (MIPSPro 7.2.1.2m compilers, Irix 6.5.3m).
|
||||
NON_GCC_TEST_OPTIONS="-D_LANGUAGE_C"
|
||||
;;
|
||||
@ -699,9 +699,9 @@ case "${canonical}" in
|
||||
# MinGW overrides and adds some system headers in nt/inc.
|
||||
GCC_TEST_OPTIONS="-I $srcdir/nt/inc"
|
||||
;;
|
||||
*-sysv4.2uw* ) opsys=unixware ;;
|
||||
*-sysv5uw* ) opsys=unixware ;;
|
||||
*-sysv5OpenUNIX* ) opsys=unixware ;;
|
||||
*-sysv4.2uw* ) opsys=unixware ;;
|
||||
*-sysv5uw* ) opsys=unixware ;;
|
||||
*-sysv5OpenUNIX* ) opsys=unixware ;;
|
||||
## Otherwise, we'll fall through to the generic opsys code at the bottom.
|
||||
esac
|
||||
;;
|
||||
@ -742,9 +742,9 @@ fi
|
||||
dnl quotation ends
|
||||
|
||||
if test $unported = yes; then
|
||||
AC_MSG_ERROR([Emacs does not support `${canonical}' systems.
|
||||
AC_MSG_ERROR([Emacs does not support '${canonical}' systems.
|
||||
If you think it should, please send a report to ${PACKAGE_BUGREPORT}.
|
||||
Check `etc/MACHINES' for recognized configuration names.])
|
||||
Check 'etc/MACHINES' for recognized configuration names.])
|
||||
fi
|
||||
|
||||
#### Choose a compiler.
|
||||
@ -1190,9 +1190,9 @@ if test "$MAKEINFO" = "no"; then
|
||||
HAVE_MAKEINFO=no
|
||||
elif test ! -e "$srcdir/info/emacs" && test ! -e "$srcdir/info/emacs.info"; then
|
||||
AC_MSG_ERROR( [You do not seem to have makeinfo >= 4.7, and your
|
||||
source tree does not seem to have pre-built manuals in the `info' directory.
|
||||
source tree does not seem to have pre-built manuals in the 'info' directory.
|
||||
Either install a suitable version of makeinfo, or re-run configure
|
||||
with the `--without-makeinfo' option to build without the manuals.] )
|
||||
with the '--without-makeinfo' option to build without the manuals.] )
|
||||
fi
|
||||
fi
|
||||
AC_SUBST(HAVE_MAKEINFO)
|
||||
@ -1216,8 +1216,8 @@ fi
|
||||
|
||||
dnl We need -znocombreloc if we're using a relatively recent GNU ld.
|
||||
dnl If we can link with the flag, it shouldn't do any harm anyhow.
|
||||
dnl (Don't use `-z nocombreloc' as -z takes no arg on Irix.)
|
||||
dnl Treat GCC specially since it just gives a non-fatal `unrecognized option'
|
||||
dnl (Don't use '-z nocombreloc' as -z takes no arg on Irix.)
|
||||
dnl Treat GCC specially since it just gives a non-fatal 'unrecognized option'
|
||||
dnl if not built to support GNU ld.
|
||||
|
||||
dnl For a long time, -znocombreloc was added to LDFLAGS rather than
|
||||
@ -1313,7 +1313,7 @@ esac
|
||||
LD_SWITCH_SYSTEM=
|
||||
case "$opsys" in
|
||||
freebsd|dragonfly)
|
||||
## Let `ld' find image libs and similar things in /usr/local/lib.
|
||||
## Let 'ld' find image libs and similar things in /usr/local/lib.
|
||||
## The system compiler, GCC, has apparently been modified to not
|
||||
## look there, contrary to what a stock GCC would do.
|
||||
### It's not our place to do this. See bug#10313#17.
|
||||
@ -1481,7 +1481,7 @@ esac
|
||||
|
||||
AC_SUBST(LIB_MATH)
|
||||
AC_DEFINE_UNQUOTED(SYSTEM_TYPE, "$SYSTEM_TYPE",
|
||||
[The type of system you are compiling for; sets `system-type'.])
|
||||
[The type of system you are compiling for; sets 'system-type'.])
|
||||
|
||||
|
||||
pre_PKG_CONFIG_CFLAGS=$CFLAGS
|
||||
@ -1536,12 +1536,12 @@ if test "${with_sound}" != "no"; then
|
||||
LIBS="$ALSA_LIBS $LIBS"
|
||||
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include <asoundlib.h>]], [[snd_lib_error_set_handler (0);]])],
|
||||
emacs_alsa_normal=yes,
|
||||
emacs_alsa_normal=no)
|
||||
emacs_alsa_normal=no)
|
||||
if test "$emacs_alsa_normal" != yes; then
|
||||
AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[#include <alsa/asoundlib.h>]],
|
||||
[[snd_lib_error_set_handler (0);]])],
|
||||
emacs_alsa_subdir=yes,
|
||||
emacs_alsa_subdir=no)
|
||||
emacs_alsa_subdir=no)
|
||||
if test "$emacs_alsa_subdir" != yes; then
|
||||
AC_MSG_ERROR([pkg-config found alsa, but it does not compile. See config.log for error messages.])
|
||||
fi
|
||||
@ -1617,7 +1617,7 @@ if test "$ac_cv_header_sys_sysinfo_h" = yes; then
|
||||
fi
|
||||
|
||||
dnl On Solaris 8 there's a compilation warning for term.h because
|
||||
dnl it doesn't define `bool'.
|
||||
dnl it doesn't define 'bool'.
|
||||
AC_CHECK_HEADERS(term.h, , , -)
|
||||
AC_HEADER_TIME
|
||||
AC_CHECK_DECLS([sys_siglist], [], [], [[#include <signal.h>
|
||||
@ -1831,7 +1831,7 @@ fail;
|
||||
CFLAGS="$CFLAGS $GNU_OBJC_CFLAGS"
|
||||
|
||||
AC_CHECK_HEADER([AppKit/AppKit.h], [HAVE_NS=yes],
|
||||
[AC_MSG_ERROR([`--with-ns' was specified, but the include
|
||||
[AC_MSG_ERROR(['--with-ns' was specified, but the include
|
||||
files are missing or cannot be compiled.])])
|
||||
|
||||
macfont_file=""
|
||||
@ -1852,7 +1852,7 @@ fail;
|
||||
AC_MSG_RESULT([$ns_osx_have_106])
|
||||
|
||||
if test $ns_osx_have_106 = no; then
|
||||
AC_MSG_ERROR([`OSX 10.6 or newer is required']);
|
||||
AC_MSG_ERROR([OSX 10.6 or newer is required]);
|
||||
fi
|
||||
fi
|
||||
fi
|
||||
@ -1910,7 +1910,7 @@ if test "${with_w32}" != no; then
|
||||
case "${opsys}" in
|
||||
cygwin)
|
||||
AC_CHECK_HEADER([windows.h], [HAVE_W32=yes],
|
||||
[AC_MSG_ERROR([`--with-w32' was specified, but windows.h
|
||||
[AC_MSG_ERROR(['--with-w32' was specified, but windows.h
|
||||
cannot be found.])])
|
||||
;;
|
||||
mingw32)
|
||||
@ -2356,7 +2356,7 @@ fail;
|
||||
fi
|
||||
|
||||
|
||||
### Use -lrsvg-2 if available, unless `--with-rsvg=no' is specified.
|
||||
### Use -lrsvg-2 if available, unless '--with-rsvg=no' is specified.
|
||||
HAVE_RSVG=no
|
||||
if test "${HAVE_X11}" = "yes" || test "${HAVE_NS}" = "yes" || test "${opsys}" = "mingw32"; then
|
||||
if test "${with_rsvg}" != "no"; then
|
||||
@ -2372,7 +2372,7 @@ if test "${HAVE_X11}" = "yes" || test "${HAVE_NS}" = "yes" || test "${opsys}" =
|
||||
CFLAGS="$CFLAGS $RSVG_CFLAGS"
|
||||
# Windows loads librsvg dynamically
|
||||
if test "${opsys}" = "mingw32"; then
|
||||
RSVG_LIBS=
|
||||
RSVG_LIBS=
|
||||
fi
|
||||
fi
|
||||
fi
|
||||
@ -2601,21 +2601,21 @@ if test "${HAVE_X11}" = "yes" && test "${with_gsettings}" = "yes"; then
|
||||
AC_MSG_CHECKING([whether GSettings is in gio])
|
||||
AC_LINK_IFELSE(
|
||||
[AC_LANG_PROGRAM(
|
||||
[[/* Check that gsettings really is present. */
|
||||
#include <glib-object.h>
|
||||
[[/* Check that gsettings really is present. */
|
||||
#include <glib-object.h>
|
||||
#include <gio/gio.h>
|
||||
]],
|
||||
[[
|
||||
]],
|
||||
[[
|
||||
GSettings *settings;
|
||||
GVariant *val = g_settings_get_value (settings, "");
|
||||
]])],
|
||||
[], HAVE_GSETTINGS=no)
|
||||
]])],
|
||||
[], HAVE_GSETTINGS=no)
|
||||
AC_MSG_RESULT([$HAVE_GSETTINGS])
|
||||
|
||||
if test "$HAVE_GSETTINGS" = "yes"; then
|
||||
AC_DEFINE(HAVE_GSETTINGS, 1, [Define to 1 if using GSettings.])
|
||||
SETTINGS_CFLAGS="$GSETTINGS_CFLAGS"
|
||||
SETTINGS_LIBS="$GSETTINGS_LIBS"
|
||||
SETTINGS_CFLAGS="$GSETTINGS_CFLAGS"
|
||||
SETTINGS_LIBS="$GSETTINGS_LIBS"
|
||||
fi
|
||||
CFLAGS=$old_CFLAGS
|
||||
LIBS=$old_LIBS
|
||||
@ -2695,7 +2695,7 @@ fi
|
||||
dnl MS Windows native file monitor is available for mingw32 only.
|
||||
case $with_file_notification,$opsys in
|
||||
w32,cygwin)
|
||||
AC_MSG_ERROR([`--with-file-notification=w32' was specified, but
|
||||
AC_MSG_ERROR(['--with-file-notification=w32' was specified, but
|
||||
this is only supported on MS-Windows native and MinGW32 builds.
|
||||
Consider using gfile instead.])
|
||||
;;
|
||||
@ -2739,7 +2739,7 @@ esac
|
||||
|
||||
case $with_file_notification,$NOTIFY_OBJ in
|
||||
yes,* | no,* | *,?*) ;;
|
||||
*) AC_MSG_ERROR([File notification `$with_file_notification' requested but requirements not found.]) ;;
|
||||
*) AC_MSG_ERROR([File notification '$with_file_notification' requested but requirements not found.]) ;;
|
||||
esac
|
||||
|
||||
if test -n "$NOTIFY_OBJ"; then
|
||||
@ -2941,7 +2941,7 @@ AC_COMPILE_IFELSE([AC_LANG_PROGRAM([[
|
||||
AC_DEFINE(HAVE_XIM, 1, [Define to 1 if XIM is available])],
|
||||
HAVE_XIM=no)
|
||||
|
||||
dnl `--with-xim' now controls only the initial value of use_xim at run time.
|
||||
dnl '--with-xim' now controls only the initial value of use_xim at run time.
|
||||
|
||||
if test "${with_xim}" != "no"; then
|
||||
AC_DEFINE(USE_XIM, 1,
|
||||
@ -2989,7 +2989,7 @@ fi
|
||||
|
||||
### Start of font-backend (under X11) section.
|
||||
if test "${HAVE_X11}" = "yes"; then
|
||||
## Use -lXft if available, unless `--with-xft=no'.
|
||||
## Use -lXft if available, unless '--with-xft=no'.
|
||||
HAVE_XFT=maybe
|
||||
if test "x${with_x}" = "xno"; then
|
||||
with_xft="no";
|
||||
@ -3094,7 +3094,7 @@ AC_SUBST(LIBOTF_LIBS)
|
||||
AC_SUBST(M17N_FLT_CFLAGS)
|
||||
AC_SUBST(M17N_FLT_LIBS)
|
||||
|
||||
### Use -lXpm if available, unless `--with-xpm=no'.
|
||||
### Use -lXpm if available, unless '--with-xpm=no'.
|
||||
### mingw32 doesn't use -lXpm, since it loads the library dynamically.
|
||||
### In the Cygwin-w32 build, we need to use /usr/include/noX/X11/xpm.h
|
||||
### rather than /usr/include/X11/xpm.h, so we set CPPFLAGS (and
|
||||
@ -3185,7 +3185,7 @@ fi
|
||||
|
||||
AC_SUBST(LIBXPM)
|
||||
|
||||
### Use -ljpeg if available, unless `--with-jpeg=no'.
|
||||
### Use -ljpeg if available, unless '--with-jpeg=no'.
|
||||
HAVE_JPEG=no
|
||||
LIBJPEG=
|
||||
if test "${with_jpeg}" != "no"; then
|
||||
@ -3249,7 +3249,7 @@ if test "${HAVE_ZLIB}" = "yes"; then
|
||||
fi
|
||||
AC_SUBST(LIBZ)
|
||||
|
||||
### Use -lpng if available, unless `--with-png=no'.
|
||||
### Use -lpng if available, unless '--with-png=no'.
|
||||
HAVE_PNG=no
|
||||
LIBPNG=
|
||||
PNG_CFLAGS=
|
||||
@ -3313,7 +3313,7 @@ fi
|
||||
AC_SUBST(LIBPNG)
|
||||
AC_SUBST(PNG_CFLAGS)
|
||||
|
||||
### Use -ltiff if available, unless `--with-tiff=no'.
|
||||
### Use -ltiff if available, unless '--with-tiff=no'.
|
||||
### mingw32 doesn't use -ltiff, since it loads the library dynamically.
|
||||
HAVE_TIFF=no
|
||||
LIBTIFF=
|
||||
@ -3341,7 +3341,7 @@ elif test "${HAVE_X11}" = "yes" || test "${HAVE_W32}" = "yes"; then
|
||||
fi
|
||||
AC_SUBST(LIBTIFF)
|
||||
|
||||
### Use -lgif or -lungif if available, unless `--with-gif=no'.
|
||||
### Use -lgif or -lungif if available, unless '--with-gif=no'.
|
||||
### mingw32 doesn't use -lgif/-lungif, since it loads the library dynamically.
|
||||
HAVE_GIF=no
|
||||
LIBGIF=
|
||||
@ -3399,7 +3399,7 @@ as options to configure])
|
||||
fi
|
||||
fi
|
||||
|
||||
### Use -lgpm if available, unless `--with-gpm=no'.
|
||||
### Use -lgpm if available, unless '--with-gpm=no'.
|
||||
HAVE_GPM=no
|
||||
LIBGPM=
|
||||
if test "${with_gpm}" != "no"; then
|
||||
@ -3537,7 +3537,7 @@ if test "${with_xml2}" != "no"; then
|
||||
CPPFLAGS="$CPPFLAGS -I$xcsdkdir/usr/include/libxml2"
|
||||
AC_CHECK_HEADER(libxml/HTMLparser.h,
|
||||
[AC_CHECK_DECL(HTML_PARSE_RECOVER, HAVE_LIBXML2=yes, ,
|
||||
[#include <libxml/HTMLparser.h>])])
|
||||
[#include <libxml/HTMLparser.h>])])
|
||||
CPPFLAGS="$SAVE_CPPFLAGS"
|
||||
if test "${HAVE_LIBXML2}" = "yes"; then
|
||||
LIBXML2_CFLAGS="-I'$xcsdkdir/usr/include/libxml2'"
|
||||
@ -3581,7 +3581,7 @@ fi
|
||||
AC_CHECK_LIB(mail, maillock, have_mail=yes, have_mail=no)
|
||||
if test $have_mail = yes; then
|
||||
LIBS_MAIL=-lmail
|
||||
AC_DEFINE(HAVE_LIBMAIL, 1, [Define to 1 if you have the `mail' library (-lmail).])
|
||||
AC_DEFINE(HAVE_LIBMAIL, 1, [Define to 1 if you have the 'mail' library (-lmail).])
|
||||
|
||||
OLD_LIBS=$LIBS
|
||||
LIBS="$LIBS_MAIL $LIBS"
|
||||
@ -3594,7 +3594,7 @@ dnl Debian, at least:
|
||||
AC_CHECK_LIB(lockfile, maillock, have_lockfile=yes, have_lockfile=no)
|
||||
if test $have_lockfile = yes; then
|
||||
LIBS_MAIL=-llockfile
|
||||
AC_DEFINE(HAVE_LIBLOCKFILE, 1, [Define to 1 if you have the `lockfile' library (-llockfile).])
|
||||
AC_DEFINE(HAVE_LIBLOCKFILE, 1, [Define to 1 if you have the 'lockfile' library (-llockfile).])
|
||||
else
|
||||
# If we have the shared liblockfile, assume we must use it for mail
|
||||
# locking (e.g. Debian). If we couldn't link against liblockfile
|
||||
@ -3606,7 +3606,7 @@ else
|
||||
if test $ac_cv_prog_liblockfile = yes; then
|
||||
AC_MSG_ERROR([Shared liblockfile found but can't link against it.
|
||||
This probably means that movemail could lose mail.
|
||||
There may be a `development' package to install containing liblockfile.])
|
||||
There may be a 'development' package to install containing liblockfile.])
|
||||
fi
|
||||
fi
|
||||
AC_CHECK_HEADERS_ONCE(maillock.h)
|
||||
@ -3624,12 +3624,12 @@ case "$opsys" in
|
||||
## On GNU/Linux systems, both methods are used by various mail programs.
|
||||
## I assume most people are using newer mailers that have heard of flock.
|
||||
## Change this if you need to.
|
||||
## Debian contains a patch which says: ``On Debian/GNU/Linux systems,
|
||||
## Debian contains a patch which says: "On Debian/GNU/Linux systems,
|
||||
## configure gets the right answers, and that means *NOT* using flock.
|
||||
## Using flock is guaranteed to be the wrong thing. See Debian Policy
|
||||
## for details.'' and then uses `#ifdef DEBIAN'. Unfortunately the
|
||||
## for details." and then uses '#ifdef DEBIAN'. Unfortunately the
|
||||
## Debian maintainer hasn't provided a clean fix for Emacs.
|
||||
## movemail.c will use `maillock' when MAILDIR, HAVE_LIBMAIL and
|
||||
## movemail.c will use 'maillock' when MAILDIR, HAVE_LIBMAIL and
|
||||
## HAVE_MAILLOCK_H are defined, so the following appears to be the
|
||||
## correct logic. -- fx
|
||||
## We must check for HAVE_LIBLOCKFILE too, as movemail does.
|
||||
@ -3689,7 +3689,7 @@ AC_CACHE_CHECK([for __builtin_unwind_init],
|
||||
emacs_cv_func___builtin_unwind_init=no)])
|
||||
if test $emacs_cv_func___builtin_unwind_init = yes; then
|
||||
AC_DEFINE(HAVE___BUILTIN_UNWIND_INIT, 1,
|
||||
[Define to 1 if you have the `__builtin_unwind_init' function.])
|
||||
[Define to 1 if you have the '__builtin_unwind_init' function.])
|
||||
fi
|
||||
|
||||
AC_CHECK_HEADERS_ONCE(sys/un.h)
|
||||
@ -3748,7 +3748,7 @@ else
|
||||
fi
|
||||
AC_MSG_RESULT([$msg])
|
||||
if test "X$msg" = Xno; then
|
||||
AC_MSG_ERROR([The required function `tputs' was not found in any library.
|
||||
AC_MSG_ERROR([The required function 'tputs' was not found in any library.
|
||||
The following libraries were tried (in order):
|
||||
libtinfo, libncurses, libterminfo, libtermcap, libcurses
|
||||
Please try installing whichever of these libraries is most appropriate
|
||||
@ -4033,7 +4033,7 @@ LIBS="$LIBS $GFILENOTIFY_LIBS"
|
||||
AC_MSG_CHECKING([whether GLib is linked in])
|
||||
AC_LINK_IFELSE([AC_LANG_PROGRAM(
|
||||
[[#include <glib.h>
|
||||
]],
|
||||
]],
|
||||
[[g_print ("Hello world");]])],
|
||||
[links_glib=yes],
|
||||
[links_glib=no])
|
||||
@ -4284,15 +4284,15 @@ case $opsys in
|
||||
esac
|
||||
|
||||
|
||||
dnl If the system's imake configuration file defines `NeedWidePrototypes'
|
||||
dnl as `NO', we must define NARROWPROTO manually. Such a define is
|
||||
dnl generated in the Makefile generated by `xmkmf'. If we don't define
|
||||
dnl If the system's imake configuration file defines 'NeedWidePrototypes'
|
||||
dnl as 'NO', we must define NARROWPROTO manually. Such a define is
|
||||
dnl generated in the Makefile generated by 'xmkmf'. If we don't define
|
||||
dnl NARROWPROTO, we will see the wrong function prototypes for X functions
|
||||
dnl taking float or double parameters.
|
||||
case $opsys in
|
||||
cygwin|gnu|gnu-linux|gnu-kfreebsd|irix6-5|freebsd|netbsd|openbsd)
|
||||
AC_DEFINE(NARROWPROTO, 1, [Define if system's imake configuration
|
||||
file defines `NeedWidePrototypes' as `NO'.])
|
||||
file defines 'NeedWidePrototypes' as 'NO'.])
|
||||
;;
|
||||
esac
|
||||
|
||||
@ -4877,8 +4877,8 @@ AC_CACHE_CHECK([for struct alignment],
|
||||
[emacs_cv_struct_alignment],
|
||||
[AC_COMPILE_IFELSE(
|
||||
[AC_LANG_PROGRAM([[#include <stddef.h>
|
||||
struct __attribute__ ((aligned (8))) s { char c; };
|
||||
struct t { char c; struct s s; };
|
||||
struct __attribute__ ((aligned (8))) s { char c; };
|
||||
struct t { char c; struct s s; };
|
||||
char verify[offsetof (struct t, s) == 8 ? 1 : -1];
|
||||
]])],
|
||||
[emacs_cv_struct_alignment=yes],
|
||||
@ -5116,7 +5116,7 @@ else
|
||||
fi
|
||||
|
||||
echo "
|
||||
Configured for \`${canonical}'.
|
||||
Configured for '${canonical}'.
|
||||
|
||||
Where should the build process find the source code? ${srcdir}
|
||||
What compiler should emacs be built with? ${CC} ${CFLAGS}
|
||||
@ -5241,7 +5241,7 @@ AC_CONFIG_FILES([$srcdir/doc/man/emacs.1])
|
||||
dnl Obviously there is duplication here wrt $SUBDIR_MAKEFILES.
|
||||
dnl You _can_ use that variable in AC_CONFIG_FILES, so long as any directory
|
||||
dnl using automake (ie lib/) is explicitly listed and not "hidden" in a variable
|
||||
dnl (else you get "no `Makefile.am' found for any configure output").
|
||||
dnl (else you get "no 'Makefile.am' found for any configure output").
|
||||
dnl This will work, but you get a config.status that is not quite right
|
||||
dnl (see http://lists.gnu.org/archive/html/bug-autoconf/2008-08/msg00028.html).
|
||||
dnl That doesn't have any obvious consequences for Emacs, but on the whole
|
||||
@ -5281,9 +5281,9 @@ dnl rather than just letting configure generate it from epaths.in.
|
||||
dnl One reason is that the various paths are not fully expanded (see above);
|
||||
dnl eg gamedir=${prefix}/var/games/emacs.
|
||||
dnl Secondly, the GNU Coding standards require that one should be able
|
||||
dnl to run `make prefix=/some/where/else' and override the values set
|
||||
dnl by configure. This also explains the `move-if-change' test and
|
||||
dnl the use of force in the `epaths-force' rule in Makefile.in.
|
||||
dnl to run 'make prefix=/some/where/else' and override the values set
|
||||
dnl by configure. This also explains the 'move-if-change' test and
|
||||
dnl the use of force in the 'epaths-force' rule in Makefile.in.
|
||||
AC_CONFIG_COMMANDS([src/epaths.h], [
|
||||
if test "${opsys}" = "mingw32"; then
|
||||
${MAKE-make} MAKEFILE_NAME=do-not-make-Makefile epaths-force-w32
|
||||
|
||||
82
make-dist
82
make-dist
@ -80,7 +80,7 @@ while [ $# -gt 0 ]; do
|
||||
new_extension=".new"
|
||||
shift
|
||||
;;
|
||||
## This option tells make-dist to use `bzip2' instead of gzip.
|
||||
## This option tells make-dist to use 'bzip2' instead of gzip.
|
||||
"--bzip2")
|
||||
default_gzip="bzip2"
|
||||
;;
|
||||
@ -132,7 +132,7 @@ done
|
||||
|
||||
### Make sure we're running in the right place.
|
||||
if [ ! -d src -o ! -f src/lisp.h -o ! -d lisp -o ! -f lisp/subr.el ]; then
|
||||
echo "${progname}: Can't find \`src/lisp.h' and \`lisp/subr.el'." >&2
|
||||
echo "${progname}: Can't find 'src/lisp.h' and 'lisp/subr.el'." >&2
|
||||
echo "${progname} must be run in the top directory of the Emacs" >&2
|
||||
echo "distribution tree. cd to that directory and try again." >&2
|
||||
exit 1
|
||||
@ -163,7 +163,7 @@ version=`
|
||||
sed -n 's/^AC_INIT(GNU Emacs,[ ]*\([^ ,)]*\).*/\1/p' <configure.ac
|
||||
` || version=
|
||||
if [ ! "${version}" ]; then
|
||||
echo "${progname}: can't find current Emacs version in \`./src/emacs.c'" >&2
|
||||
echo "${progname}: can't find current Emacs version in './src/emacs.c'" >&2
|
||||
exit 1
|
||||
fi
|
||||
|
||||
@ -190,10 +190,10 @@ fi
|
||||
### Make sure the subdirectory is available.
|
||||
tempparent="make-dist.tmp.$$"
|
||||
if [ -d ${tempparent} ]; then
|
||||
echo "${progname}: staging directory \`${tempparent}' already exists.
|
||||
Perhaps a previous invocation of \`${progname}' failed to clean up after
|
||||
echo "${progname}: staging directory '${tempparent}' already exists.
|
||||
Perhaps a previous invocation of '${progname}' failed to clean up after
|
||||
itself. Check that directories whose names are of the form
|
||||
\`make-dist.tmp.NNNNN' don't contain any important information, remove
|
||||
'make-dist.tmp.NNNNN' don't contain any important information, remove
|
||||
them, and try again." >&2
|
||||
exit 1
|
||||
fi
|
||||
@ -210,7 +210,7 @@ if [ $check = yes ]; then
|
||||
## Check for .elc files with no corresponding .el file.
|
||||
sed 's/\.el$/.elc/' /tmp/el > /tmp/elelc
|
||||
|
||||
bogosities="`comm -13 /tmp/elelc /tmp/elc`"
|
||||
bogosities=`comm -13 /tmp/elelc /tmp/elc`
|
||||
if [ x"${bogosities}" != x"" ]; then
|
||||
echo "The following .elc files have no corresponding .el files:"
|
||||
echo "${bogosities}"
|
||||
@ -218,7 +218,7 @@ if [ $check = yes ]; then
|
||||
|
||||
### Check for .el files with no corresponding .elc file.
|
||||
sed 's/\.elc$/.el/' /tmp/elc > /tmp/elcel
|
||||
losers="`comm -23 /tmp/el /tmp/elcel`"
|
||||
losers=`comm -23 /tmp/el /tmp/elcel`
|
||||
|
||||
rm -f /tmp/el /tmp/elc /tmp/elcel /tmp/elelc
|
||||
|
||||
@ -263,7 +263,7 @@ if [ $update = yes ]; then
|
||||
$EMACS -batch -f batch-byte-recompile-directory lisp
|
||||
fi # $update = yes
|
||||
|
||||
echo "Creating staging directory: \`${tempparent}'"
|
||||
echo "Creating staging directory: '${tempparent}'"
|
||||
|
||||
mkdir ${tempparent}
|
||||
tempdir="${tempparent}/${emacsname}"
|
||||
@ -274,7 +274,7 @@ if [ "${clean_up}" = yes ]; then
|
||||
trap "echo 'Cleaning up the staging directory'; rm -rf ${tempparent}" EXIT
|
||||
fi
|
||||
|
||||
echo "Creating top directory: \`${tempdir}'"
|
||||
echo "Creating top directory: '${tempdir}'"
|
||||
mkdir ${tempdir}
|
||||
|
||||
if test -d .git; then
|
||||
@ -325,7 +325,7 @@ do
|
||||
mkdir ${tempdir}/${subdir}
|
||||
done
|
||||
|
||||
echo "Making links to \`lisp' and its subdirectories"
|
||||
echo "Making links to 'lisp' and its subdirectories"
|
||||
files=`find lisp \( -name '*.el' -o -name '*.elc' -o -name 'ChangeLog*' \
|
||||
-o -name 'README' \)`
|
||||
|
||||
@ -337,7 +337,7 @@ for file in lisp/Makefile.in lisp/makefile.w32-in $files; do
|
||||
ln $file $tempdir/$file
|
||||
done
|
||||
|
||||
echo "Making links to \`leim' and its subdirectories"
|
||||
echo "Making links to 'leim' and its subdirectories"
|
||||
(cd leim
|
||||
ln makefile.w32-in ../${tempdir}/leim
|
||||
ln ChangeLog.*[0-9] README ../${tempdir}/leim
|
||||
@ -348,7 +348,7 @@ echo "Making links to \`leim' and its subdirectories"
|
||||
ln leim-ext.el ../${tempdir}/leim/leim-ext.el)
|
||||
|
||||
## FIXME Can we not just use the "find -type f" method for this one?
|
||||
echo "Making links to \`build-aux'"
|
||||
echo "Making links to 'build-aux'"
|
||||
(cd build-aux
|
||||
ln compile config.guess config.sub depcomp msys-to-w32 ../${tempdir}/build-aux
|
||||
ln gitlog-to-changelog gitlog-to-emacslog ../${tempdir}/build-aux
|
||||
@ -356,11 +356,11 @@ echo "Making links to \`build-aux'"
|
||||
ln update-copyright update-subdirs ../${tempdir}/build-aux
|
||||
ln dir_top make-info-dir ../${tempdir}/build-aux)
|
||||
|
||||
echo "Making links to \`build-aux/snippet'"
|
||||
echo "Making links to 'build-aux/snippet'"
|
||||
(cd build-aux/snippet
|
||||
ln *.h ../../${tempdir}/build-aux/snippet)
|
||||
|
||||
echo "Making links to \`src'"
|
||||
echo "Making links to 'src'"
|
||||
### Don't distribute the configured versions of
|
||||
### config.in, paths.in, buildobj.h, or Makefile.in.
|
||||
(cd src
|
||||
@ -374,11 +374,11 @@ echo "Making links to \`src'"
|
||||
cd ../${tempdir}/src
|
||||
rm -f globals.h config.h epaths.h Makefile buildobj.h)
|
||||
|
||||
echo "Making links to \`src/bitmaps'"
|
||||
echo "Making links to 'src/bitmaps'"
|
||||
(cd src/bitmaps
|
||||
ln README *.xbm ../../${tempdir}/src/bitmaps)
|
||||
|
||||
echo "Making links to \`lib'"
|
||||
echo "Making links to 'lib'"
|
||||
(snippet_h=`(cd build-aux/snippet && ls *.h)`
|
||||
cd lib
|
||||
ln [a-zA-Z]*.[ch] ../${tempdir}/lib
|
||||
@ -387,7 +387,7 @@ echo "Making links to \`lib'"
|
||||
script='/[*]/d; s/\.in\.h$/.h/'
|
||||
rm -f `(echo "$snippet_h"; ls *.in.h) | sed "$script"`)
|
||||
|
||||
echo "Making links to \`lib-src'"
|
||||
echo "Making links to 'lib-src'"
|
||||
(cd lib-src
|
||||
ln [a-zA-Z]*.[ch] ../${tempdir}/lib-src
|
||||
ln ChangeLog.*[0-9] Makefile.in README ../${tempdir}/lib-src
|
||||
@ -395,11 +395,11 @@ echo "Making links to \`lib-src'"
|
||||
ln makefile.w32-in ../${tempdir}/lib-src
|
||||
ln update-game-score.exe.manifest ../${tempdir}/lib-src)
|
||||
|
||||
echo "Making links to \`m4'"
|
||||
echo "Making links to 'm4'"
|
||||
(cd m4
|
||||
ln *.m4 ../${tempdir}/m4)
|
||||
|
||||
echo "Making links to \`nt'"
|
||||
echo "Making links to 'nt'"
|
||||
(cd nt
|
||||
ln emacs-x86.manifest emacs-x64.manifest ../${tempdir}/nt
|
||||
ln config.nt emacs-src.tags ../${tempdir}/nt
|
||||
@ -408,55 +408,55 @@ echo "Making links to \`nt'"
|
||||
ln mingw-cfg.site epaths.nt INSTALL.OLD ../${tempdir}/nt
|
||||
ln ChangeLog.*[0-9] INSTALL README README.W32 makefile.w32-in ../${tempdir}/nt)
|
||||
|
||||
echo "Making links to \`nt/inc' and its subdirectories"
|
||||
echo "Making links to 'nt/inc' and its subdirectories"
|
||||
for f in `find nt/inc -type f -name '[a-z]*.h'`; do
|
||||
ln $f $tempdir/$f
|
||||
done
|
||||
|
||||
echo "Making links to \`nt/icons'"
|
||||
echo "Making links to 'nt/icons'"
|
||||
(cd nt/icons
|
||||
ln README [a-z]*.ico ../../${tempdir}/nt/icons
|
||||
ln [a-z]*.cur ../../${tempdir}/nt/icons)
|
||||
|
||||
echo "Making links to \`msdos'"
|
||||
echo "Making links to 'msdos'"
|
||||
(cd msdos
|
||||
ln ChangeLog.*[0-9] INSTALL README emacs.ico emacs.pif ../${tempdir}/msdos
|
||||
ln depfiles.bat inttypes.h ../${tempdir}/msdos
|
||||
ln mainmake.v2 sed*.inp ../${tempdir}/msdos)
|
||||
|
||||
echo "Making links to \`nextstep'"
|
||||
echo "Making links to 'nextstep'"
|
||||
(cd nextstep
|
||||
ln ChangeLog.*[0-9] README INSTALL Makefile.in ../${tempdir}/nextstep)
|
||||
|
||||
echo "Making links to \`nextstep/templates'"
|
||||
echo "Making links to 'nextstep/templates'"
|
||||
(cd nextstep/templates
|
||||
ln Emacs.desktop.in Info-gnustep.plist.in Info.plist.in InfoPlist.strings.in ../../${tempdir}/nextstep/templates)
|
||||
|
||||
echo "Making links to \`nextstep/Cocoa/Emacs.base/Contents'"
|
||||
echo "Making links to 'nextstep/Cocoa/Emacs.base/Contents'"
|
||||
(cd nextstep/Cocoa/Emacs.base/Contents
|
||||
ln PkgInfo ../../../../${tempdir}/nextstep/Cocoa/Emacs.base/Contents)
|
||||
|
||||
echo "Making links to \`nextstep/Cocoa/Emacs.base/Contents/Resources'"
|
||||
echo "Making links to 'nextstep/Cocoa/Emacs.base/Contents/Resources'"
|
||||
(cd nextstep/Cocoa/Emacs.base/Contents/Resources
|
||||
ln Credits.html *.icns ../../../../../${tempdir}/nextstep/Cocoa/Emacs.base/Contents/Resources)
|
||||
|
||||
echo "Making links to \`nextstep/GNUstep/Emacs.base/Resources'"
|
||||
echo "Making links to 'nextstep/GNUstep/Emacs.base/Resources'"
|
||||
(cd nextstep/GNUstep/Emacs.base/Resources
|
||||
ln README emacs.tiff ../../../../${tempdir}/nextstep/GNUstep/Emacs.base/Resources )
|
||||
|
||||
echo "Making links to \`oldXMenu'"
|
||||
echo "Making links to 'oldXMenu'"
|
||||
(cd oldXMenu
|
||||
ln *.[ch] *.in *.mk ../${tempdir}/oldXMenu
|
||||
ln README ChangeLog.*[0-9] ../${tempdir}/oldXMenu)
|
||||
|
||||
echo "Making links to \`lwlib'"
|
||||
echo "Making links to 'lwlib'"
|
||||
(cd lwlib
|
||||
ln *.[ch] *.in *.mk ../${tempdir}/lwlib
|
||||
ln README ChangeLog.*[0-9] ../${tempdir}/lwlib)
|
||||
|
||||
## It is important to distribute admin/ because it contains sources
|
||||
## for generated lisp/international/uni-*.el files.
|
||||
echo "Making links to \`admin' and its subdirectories"
|
||||
echo "Making links to 'admin' and its subdirectories"
|
||||
for f in `find admin -type f`; do
|
||||
case $f in
|
||||
*/Makefile) [ -f $f.in ] && continue ;;
|
||||
@ -465,7 +465,7 @@ for f in `find admin -type f`; do
|
||||
done
|
||||
|
||||
if [ "$with_tests" = "yes" ]; then
|
||||
echo "Making links to \`test' and its subdirectories"
|
||||
echo "Making links to 'test' and its subdirectories"
|
||||
for f in `find test -type f`; do
|
||||
case $f in
|
||||
test/automated/*.log) continue ;;
|
||||
@ -476,7 +476,7 @@ if [ "$with_tests" = "yes" ]; then
|
||||
done
|
||||
fi
|
||||
|
||||
echo "Making links to \`etc' and its subdirectories"
|
||||
echo "Making links to 'etc' and its subdirectories"
|
||||
for f in `find etc -type f`; do
|
||||
case $f in
|
||||
etc/DOC*|etc/*.pyc) continue ;;
|
||||
@ -487,32 +487,32 @@ for f in `find etc -type f`; do
|
||||
ln $f $tempdir/$f
|
||||
done
|
||||
|
||||
echo "Making links to \`info'"
|
||||
echo "Making links to 'info'"
|
||||
ln `find info -type f -print` ${tempdir}/info
|
||||
|
||||
echo "Making links to \`doc/emacs'"
|
||||
echo "Making links to 'doc/emacs'"
|
||||
(cd doc/emacs
|
||||
ln *.texi *.in makefile.w32-in ChangeLog.*[0-9] ../../${tempdir}/doc/emacs)
|
||||
|
||||
echo "Making links to \`doc/misc'"
|
||||
echo "Making links to 'doc/misc'"
|
||||
(cd doc/misc
|
||||
ln *.texi *.tex *.in makefile.w32-in gnus-news.el ChangeLog.*[0-9] \
|
||||
../../${tempdir}/doc/misc)
|
||||
|
||||
echo "Making links to \`doc/lispref'"
|
||||
echo "Making links to 'doc/lispref'"
|
||||
(cd doc/lispref
|
||||
ln *.texi *.in makefile.w32-in README ChangeLog.*[0-9] \
|
||||
../../${tempdir}/doc/lispref
|
||||
ln spellfile ../../${tempdir}/doc/lispref
|
||||
ln two-volume.make two-volume-cross-refs.txt ../../${tempdir}/doc/lispref)
|
||||
|
||||
echo "Making links to \`doc/lispintro'"
|
||||
echo "Making links to 'doc/lispintro'"
|
||||
(cd doc/lispintro
|
||||
ln *.texi *.in makefile.w32-in *.eps *.pdf ../../${tempdir}/doc/lispintro
|
||||
ln README ChangeLog.*[0-9] ../../${tempdir}/doc/lispintro
|
||||
cd ../../${tempdir}/doc/lispintro)
|
||||
|
||||
echo "Making links to \`doc/man'"
|
||||
echo "Making links to 'doc/man'"
|
||||
(cd doc/man
|
||||
ln *.*[0-9] *.in ../../${tempdir}/doc/man
|
||||
cd ../../${tempdir}/doc/man
|
||||
@ -520,7 +520,7 @@ echo "Making links to \`doc/man'"
|
||||
|
||||
### It would be nice if they could all be symlinks to top-level copy, but
|
||||
### you're not supposed to have any symlinks in distribution tar files.
|
||||
echo "Making sure copying notices are all copies of \`COPYING'"
|
||||
echo "Making sure copying notices are all copies of 'COPYING'"
|
||||
for subdir in . etc leim lib lib-src lisp lwlib msdos nt src; do
|
||||
rm -f ${tempdir}/${subdir}/COPYING
|
||||
cp COPYING ${tempdir}/${subdir}
|
||||
@ -548,7 +548,7 @@ if [ "${make_tar}" = yes ]; then
|
||||
found=1; break
|
||||
done
|
||||
if [ "$found" = "0" ]; then
|
||||
echo "WARNING: \`$default_gzip' not found, will not compress" >&2
|
||||
echo "WARNING: '$default_gzip' not found, will not compress" >&2
|
||||
default_gzip=cat
|
||||
fi
|
||||
case "${default_gzip}" in
|
||||
|
||||
Loading…
Reference in New Issue
Block a user