gnuastro-devel
[Top][All Lists]
Advanced

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

[gnuastro-devel] [bug #47987] doc/genauthors makes an empty doc/authors.


From: Mohammad Akhlaghi
Subject: [gnuastro-devel] [bug #47987] doc/genauthors makes an empty doc/authors.texi in multiple threads
Date: Mon, 23 May 2016 11:34:57 +0000 (UTC)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0

URL:
  <http://savannah.gnu.org/bugs/?47987>

                 Summary: doc/genauthors makes an empty doc/authors.texi in
multiple threads
                 Project: GNU Astronomy Utilities
            Submitted by: makhlaghi
            Submitted on: Mon 23 May 2016 08:34:55 PM JST
                Category: Development
                Severity: 3 - Normal
              Item Group: Crash
                  Status: Confirmed
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any

    _______________________________________________________

Details:

When `make' is called on multiple threads, sometimes the `git shortlog'
command in `doc/genauthors' doesn't make any output. Therefore `authors.texi'
remains empty. 

In commit c5b6cee (Check added to see if doc/authors.texi is empty) a test was
added to check if `doc/authors.texi' is empty. If so, `doc/genauthors' exits
with a non-zero value (failure). So the building process stops and the
user/developer is informed. By running a simple `make' it will be built, and
since the documentation is the last part to be built, there won't be any
problem with building the libraries and utilities.

However, this is not an elegant solution! We have to find a solution, so `git
shortlog' makes an output everytime `make -jN' is run, not randomly.




    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?47987>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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