[bug #63362] make 4.4: different behavior with -j1 and -j2 when building manpages from git

[Alexander Kanavin]

URL:
  <https://savannah.gnu.org/bugs/?63362>

                 Summary: make 4.4: different behavior with -j1 and -j2 when
building manpages from git
                 Project: make
               Submitter: kanavin
               Submitted: Mon 14 Nov 2022 10:04:36 AM UTC
                Severity: 3 - Normal
              Item Group: Bug
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
       Component Version: 4.4
        Operating System: POSIX-Based
           Fixed Release: None
           Triage Status: None


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Mon 14 Nov 2022 10:04:36 AM UTC By: Alexander Kanavin <kanavin>
When building git v2.38.1
(https://github.com/git/git/tags)

I noticed that make 4.4 behaves differently depending on parallelism
settings.

 
alex@alex-lx-laptop:~/development/git/Documentation$ ../../make-4.4/make -j1
git-add.1
    SUBDIR ../
make[1]: 'GIT-VERSION-FILE' is up to date.
 
vs
 
alex@alex-lx-laptop:~/development/git/Documentation$ ../../make-4.4/make -j2
git-add.1
    SUBDIR ../
make[1]: 'GIT-VERSION-FILE' is up to date.
    XMLTO git-add.1
Makefile:355: warning: pattern recipe did not update peer target 'git-add.7'.
Makefile:355: warning: pattern recipe did not update peer target 'git-add.5'.
 

Manpages are rebuilt without need, if j is more than one. I believe this is
triggered by FORCE flag for one of the rules in the makefile, but still the
difference in behavior depending on what is in -j does not seem correct.
https://github.com/git/git/blob/v2.38.1/Documentation/Makefile#L326

I also confirmed that with make 4.3 this does not happen: manpages are not
rebuilt, regardless of -j. FORCE does not have an effect on this.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63362>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/