summaryrefslogtreecommitdiffstats
path: root/package/python3/0007-Abort-on-failed-module-build.patch
diff options
context:
space:
mode:
Diffstat (limited to 'package/python3/0007-Abort-on-failed-module-build.patch')
-rw-r--r--package/python3/0007-Abort-on-failed-module-build.patch30
1 files changed, 30 insertions, 0 deletions
diff --git a/package/python3/0007-Abort-on-failed-module-build.patch b/package/python3/0007-Abort-on-failed-module-build.patch
new file mode 100644
index 0000000000..09aa47211a
--- /dev/null
+++ b/package/python3/0007-Abort-on-failed-module-build.patch
@@ -0,0 +1,30 @@
+From 03936d5f998e60f234617b41f85053ea10b7a3d8 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 09fc3ee..0be015e 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.9.3
+
OpenPOWER on IntegriCloud