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>
This commit is contained in:
Thomas Petazzoni 2015-08-28 15:03:34 +02:00
parent a0f3a2b88d
commit 4c19d83ed5

View File

@ -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))