On 2013-09-18 22:12:42 +0200, Kurt Roeckx wrote:
> If you do not want to use the version with the highest number, I
> suggest you remove it.
Perhaps, but AFAIK, this is not documented (and if it is, this is
hidden somewhere).
> At any time you install something ldconfig is going to be run and
> update it to point to the latest version.
This is not what is documented. The libtool manual says that ldconfig
is to be run manually via "libtool -n finish ..." (if the user wants
too):
Then, running 'libtool -n finish LIBDIR' can give you further hints
on what to do (*note Finish mode::):
burger# libtool -n finish /usr/local/lib
PATH="$PATH:/sbin" ldconfig -m /usr/local/lib
-----------------------------------------------------------------
Libraries have been installed in:
/usr/local/lib
To link against installed libraries in a given directory, LIBDIR,
you must use the `-LLIBDIR' flag during linking.
You will also need to do one of the following:
- add LIBDIR to the `LD_LIBRARY_PATH' environment variable
during execution
- add LIBDIR to the `LD_RUN_PATH' environment variable
during linking
- use the `-RLIBDIR' linker flag
See any operating system documentation about shared libraries for
more information, such as the ld and ld.so manual pages.
-----------------------------------------------------------------
burger#
> That is what ldconfig is supposed to do.
But my point is that it shouldn't be run by "make install".
The Automake manual says:
After everything has been built, and maybe tested, it is time to
install it on the system. That means copying the programs, libraries,
header files, scripts, and other data files from the source directory to
their final destination on the system. The command 'make install' will
do that.
That's just installation of files, not running ldconfig.
> > Moreover, in most documentation, it is said that to install some
> > software, the process is "./configure && make && make install" (and
> > one assumes that the software that has just been installed is ready
> > to be used, if the user's path environment variables are up-to-date,
> > of course). But this is not the case with the current behavior.
>
> I think that also assumes you want to install a newer version,
> where newer is a higher number. That might at that time not
> run ldconfig, but more then likely it will get run at some point.
ldconfig should normally be run only when the user instructs to do so.
--
Vincent Lefèvre <vinc...@vinc17.net> - Web: <http://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
