[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnulib] gettext-0.12-pre2 available for testing

From: Bruno Haible
Subject: [Bug-gnulib] gettext-0.12-pre2 available for testing
Date: Sat, 29 Mar 2003 13:31:43 +0100 (CET)

The second prerelease of gettext-0.12:


This is a test release of GNU gettext.  Please do not send reports
about this release to any GNU mailing list or newsgroup. Please send
comments and problems to <bruno at clisp.org>.

Note that test release numbers cannot be given as argument to the "autopoint"
program. Therefore please don't use the "gettextize" program of this test
release on projects which you share with other programmers via CVS.

This prerelease for the first time features a relocatable installation.
Quoting the INSTALL file:

Relocatable Installation

   By default, `make install' will install a package with hardwired
file names, and the package will not work correctly when copied or
moved to a different location in the filesystem.

   Some packages pay attention to the `--enable-relocatable' option to
`configure'.  This option makes the entire installed package
relocatable.  This means, it can be moved or copied to a different
location on the filesystem.  It is possible to make symlinks to the
installed and moved programs, and invoke them through the symlink.  It
is possible to do the same thing  with a hard link _only_ if the hard
linked file is in the same directory as the real program.

   For reliability it is best to give together with --enable-relocatable
a `--prefix' option pointing to an otherwise unused (and never used
again) directory, for example, `--prefix=/tmp/inst$$'.  This is
recommended because on some OSes the executables remember the location
of shared libraries (and prefer them over LD_LIBRARY_PATH !), therefore
such an executable will look for its shared libraries first in the
original installation directory and only then in the current
installation directory.

   Installation with `--enable-relocatable' will not work for setuid /
setgid executables.  (This is because such an executable kills its
LD_LIBRARY_PATH variable when it is launched.)

   The runtime penalty and size penalty are nearly zero on Linux 2.2 or
newer (just one system call more when an executable is launched), and
small on other systems (the wrapper program just sets an environment
variable and execs the real program).

reply via email to

[Prev in Thread] Current Thread [Next in Thread]