[PR #257] [MERGED] Force MAKEFLAGS to --jobs=1 to ensure dependencies are executed sequentially and in correct order #1255

New issue

Closed

opened 2026-05-07 01:01:14 +02:00 by BreizhHardware · 0 comments

BreizhHardware commented

2026-05-07 01:01:14 +02:00

Owner

📋 Pull Request Information

Original PR: https://github.com/binwiederhier/ntfy/pull/257
Author: @oddlama
Created: 5/16/2022
Status: ✅ Merged
Merged: 5/16/2022
Merged by: @binwiederhier

Base: main ← Head: disable-makefile-paralellism

📝 Commits (1)

6c2aa0c Force MAKEFLAGS to --jobs=1 to ensure dependencies are executed

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 Makefile (+1 -0)

📄 Description

If this is not set, make -j2 web or higher job counts will
cause the build to fail as some dependencies are not expressed
directly on the dependent tasks but as a dependency list
on a parent task.

Alternatively one could add the required dependencies for each
task separately, but that would factually sequentiallize the
build, so there's no real difference except this approach
fixes all dependency chains globally.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/binwiederhier/ntfy/pull/257 **Author:** [@oddlama](https://github.com/oddlama) **Created:** 5/16/2022 **Status:** ✅ Merged **Merged:** 5/16/2022 **Merged by:** [@binwiederhier](https://github.com/binwiederhier) **Base:** `main` ← **Head:** `disable-makefile-paralellism` --- ### 📝 Commits (1) - [`6c2aa0c`](https://github.com/binwiederhier/ntfy/commit/6c2aa0c3c2b05943558b160f5c65849d6e8be51b) Force MAKEFLAGS to --jobs=1 to ensure dependencies are executed ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `Makefile` (+1 -0) </details> ### 📄 Description If this is not set, make -j2 web or higher job counts will cause the build to fail as some dependencies are not expressed directly on the dependent tasks but as a dependency list on a parent task. Alternatively one could add the required dependencies for each task separately, but that would factually sequentiallize the build, so there's no real difference except this approach fixes all dependency chains globally. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>