gnuastro-commits
[Top][All Lists]
Advanced

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

[gnuastro-commits] master e98d9b0: Minor editing in Known issue item


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master e98d9b0: Minor editing in Known issue item
Date: Sun, 23 Oct 2016 16:43:51 +0000 (UTC)

branch: master
commit e98d9b09a82d8f76417798dcfa13e18a876c42a7
Author: Mohammad Akhlaghi <address@hidden>
Commit: Mohammad Akhlaghi <address@hidden>

    Minor editing in Known issue item
    
    The known issue item that was added in the previous commit (98b31bd) was
    slightly edited to be more readable.
---
 doc/gnuastro.texi |   23 ++++++++++++-----------
 1 file changed, 12 insertions(+), 11 deletions(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index e0059d4..80f40fd 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -3855,17 +3855,18 @@ address@hidden@url{https://www.tug.org/texlive/}}.
 
 @item
 @cindex GNU Libtool
-After @code{make check}: not copy the programs' executables to the
-installation directory manually (using @command{cp} for example). In
-default address@hidden you configure Gnuastro with the
address@hidden option, then the libraries will be statically
-linked to the programs and this problem won't exist, see @ref{Linking}.},
-the program binaries need to link with Gnuastro's shared library which is
-also installed with the programs. Therefore, to run successfully before and
-after installation, linking modifications need to be made by GNU Libtool at
-installation time. @command{make install} does this internally, but a
-simple copy might give linking errors when you run it. If you need to copy
-the executables, you can do so after installation.
+After @code{make check}: do not copy the programs' executables to another
+(for example, the installation) directory manually (using @command{cp}, or
address@hidden for example). In the default address@hidden you
+configure Gnuastro with the @option{--disable-shared} option, then the
+libraries will be statically linked to the programs and this problem won't
+exist, see @ref{Linking}.}, the program binaries need to link with
+Gnuastro's shared library which is also built and installed with the
+programs. Therefore, to run successfully before and after installation,
+linking modifications need to be made by GNU Libtool at installation
+time. @command{make install} does this internally, but a simple copy might
+give linking errors when you run it. If you need to copy the executables,
+you can do so after installation.
 
 @end itemize
 



reply via email to

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