summaryrefslogtreecommitdiffstats
path: root/package/python3/0010-Abort-on-failed-module-build.patch
diff options
context:
space:
mode:
Diffstat (limited to 'package/python3/0010-Abort-on-failed-module-build.patch')
-rw-r--r--package/python3/0010-Abort-on-failed-module-build.patch30
1 files changed, 0 insertions, 30 deletions
diff --git a/package/python3/0010-Abort-on-failed-module-build.patch b/package/python3/0010-Abort-on-failed-module-build.patch
deleted file mode 100644
index 74342da0ca..0000000000
--- a/package/python3/0010-Abort-on-failed-module-build.patch
+++ /dev/null
@@ -1,30 +0,0 @@
-From 01780527e647b15f7f1aed4351c18fb4098a8707 Mon Sep 17 00:00:00 2001
-From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-Date: Wed, 23 Dec 2015 11:43:24 +0100
-Subject: [PATCH] Abort on failed module build
-
-When building a Python module fails, the setup.py script currently
-doesn't exit with an error, and simply continues. This is not a really
-nice behavior, so this patch changes setup.py to abort with an error,
-so that the build issue is clearly noticeable.
-
-Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
----
- setup.py | 1 +
- 1 file changed, 1 insertion(+)
-
-diff --git a/setup.py b/setup.py
-index 9a48d5f..d02012d 100644
---- a/setup.py
-+++ b/setup.py
-@@ -312,6 +312,7 @@ class PyBuildExt(build_ext):
- print("Failed to build these modules:")
- print_three_column(failed)
- print()
-+ sys.exit(1)
-
- if self.failed_on_import:
- failed = self.failed_on_import[:]
---
-2.7.4
-
OpenPOWER on IntegriCloud