aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2015-08-28 15:03:34 +0200
committerGravatar Thomas Petazzoni <thomas.petazzoni@free-electrons.com>2015-08-28 15:03:34 +0200
commit4c19d83ed5a8c2f1163e9ad84a74f3a75d3a5ba9 (patch)
treec19f1fc6f49f28f4fc38f3f45e41cd53eb39e49d
parenta0f3a2b88d27df6f3e8e3d45bd8a0506a3d09455 (diff)
downloadbuildroot-4c19d83ed5a8c2f1163e9ad84a74f3a75d3a5ba9.tar.gz
buildroot-4c19d83ed5a8c2f1163e9ad84a74f3a75d3a5ba9.tar.bz2
python-can: remove incorrect dependency
When using the python-package infrastructure, there is no need for packages to declare a dependency on the Python interpreter: the package infrastructure does it automatically. Moreover, this is actually broken in the case of python-can, which can be selected either with Python 2.x or Python 3.x. If the latter is chosen, python-can will still trigger the build of Python 2.x, which is incorrect. This was discovered by Vicente Olivert Riera during the analysis of the following build failure: http://autobuild.buildroot.net/results/aff/affb1d4a328c479be73b7818364db5914bf3d376/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
-rw-r--r--package/python-can/python-can.mk1
1 files changed, 0 insertions, 1 deletions
diff --git a/package/python-can/python-can.mk b/package/python-can/python-can.mk
index 8db5732ff6..53d5e0f694 100644
--- a/package/python-can/python-can.mk
+++ b/package/python-can/python-can.mk
@@ -9,7 +9,6 @@ PYTHON_CAN_SITE = https://bitbucket.org/hardbyte/python-can/get/
PYTHON_CAN_SOURCE = $(PYTHON_CAN_VERSION).tar.bz2
PYTHON_CAN_LICENSE = LGPLv3
PYTHON_CAN_LICENSE_FILES = LICENSE.txt
-PYTHON_CAN_DEPENDENCIES = python
PYTHON_CAN_SETUP_TYPE = setuptools
$(eval $(python-package))