forked from buildroot/buildroot
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
package/cpulimit: Remove or1k/musl limitation
It turns out that we can build cpulimit for or1k using musl-libc if we remove the inclusion of the problematic procfs.h header file which is not required at all. This is a backport of the following upstream pull request: opsengine/cpulimit#110 Signed-off-by: Florian Fainelli <[email protected]>
- Loading branch information
Showing
2 changed files
with
32 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
From 48a88c033c5704d37645051ca51799a8b5a7e059 Mon Sep 17 00:00:00 2001 | ||
From: Florian Fainelli <[email protected]> | ||
Date: Thu, 19 May 2022 14:22:40 -0700 | ||
Subject: [PATCH] Remove procfs.h inclusion | ||
|
||
We do not use anything from this header | ||
|
||
Signed-off-by: Florian Fainelli <[email protected]> | ||
[Upstream: https://github.com/opsengine/cpulimit/pull/110] | ||
--- | ||
src/process_iterator.c | 3 --- | ||
1 file changed, 3 deletions(-) | ||
|
||
diff --git a/src/process_iterator.c b/src/process_iterator.c | ||
index 8b4019d237f2..5b6c651bc5d0 100644 | ||
--- a/src/process_iterator.c | ||
+++ b/src/process_iterator.c | ||
@@ -22,9 +22,6 @@ | ||
#include <stdio.h> | ||
#include <stdlib.h> | ||
#include <string.h> | ||
-#ifndef __APPLE__ | ||
-#include <sys/procfs.h> | ||
-#endif | ||
#include <time.h> | ||
#include "process_iterator.h" | ||
|
||
-- | ||
2.25.1 | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters