On 02/09/2018 02:25 AM, Russell Peterson wrote:
The package I was adding had python scripts in it. The make process for the package used the python distutils.core setup function. I didn’t write the code… I’m just creating a recipe for it. This in turn copies the scripts to various locations but in the process of doing that modifies the #! at the start of the script to use the hosttools path to python. Not very cross-build friendly. I simply patched the makefile to use the —executable=/usr/bin/python argument. All this does is prevent the #! modification. Builds fine now. Bit of a hack but I will speak with the developers to create a bit more cross build friendly options.
This is actually a common issue, and we routinely patch python scripts after-the-fact to replace upstream's idea of where python is with something sane. I'd say you can almost always just hardcode
#!/usr/bin/en python3 in there. Alex -- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
