gnuastro-commits
[Top][All Lists]
Advanced

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

[gnuastro-commits] master 98b31bd: Explanation to not copy built program


From: Mohammad Akhlaghi
Subject: [gnuastro-commits] master 98b31bd: Explanation to not copy built programs
Date: Sun, 23 Oct 2016 16:26:40 +0000 (UTC)

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

    Explanation to not copy built programs
    
    Following Francesco's explanations in sr #109171, an item was added to the
    "Known issues" section of the manual, explaining that the built program
    executables must not be copied before `make install'.
---
 doc/gnuastro.texi |   16 +++++++++++++++-
 1 file changed, 15 insertions(+), 1 deletion(-)

diff --git a/doc/gnuastro.texi b/doc/gnuastro.texi
index b0cfc64..e0059d4 100644
--- a/doc/gnuastro.texi
+++ b/doc/gnuastro.texi
@@ -658,7 +658,7 @@ $ sudo make install
 
 @noindent
 
-See @ref{Known issues} if you confront any complications.  For each program
+See @ref{Known issues} if you confront any complications. For each program
 there is an `Invoke ProgramName' sub-section in this book which explains
 how the programs should be run on the command-line. You can read it on the
 command-line by running the command @command{$ info astprogname}, see
@@ -3853,6 +3853,20 @@ program, the more recent the better). A working @TeX{} 
program is also
 necessary, which you can get from Tex
 address@hidden@url{https://www.tug.org/texlive/}}.
 
address@hidden
address@hidden 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.
+
 @end itemize
 
 @noindent



reply via email to

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