Benjamin Fogle

Building a wheel for an embedded platform is an intended use case for crossenv. While I haven't tested this on a powerpc target yet, if you have successfully compiled Python...

No, I don't think you'll need to rename anything, and those file names are a good sign that everything is working. What your seeing is a [PEP3149](https://www.python.org/dev/peps/pep-3149/) ABI-tagged .so file,...

Libxml2 is a C library that the lxml uses, along with libxslt. Lxml requires both to build and to run. You will need to do the following: 1. Download libxml2...

That's a very interesting idea. I'm not sure I know PyInstaller well enough to be of much help, unfortunately. Looking at that message, it looks like it couldn't figure out...

Usually when I've seen errors like that (outside of crossenv), the fix was to add a `[target]` section to `~/.cargo/config`: ```ini [target.arm-unknown-linux-gnueabihf] linker = "/home/serg/crscmpl/imx6bh4/host/usr/bin/arm-buildroot-linux-gnueabihf-gcc" ``` There's also the possibility...

This could be tricky to solve in a clean manner. Rust build scripts mean that there's a native compilation step mixed in with cross-compilation steps in a way we have...

Thanks for waiting while I got to this. I am having trouble reproducing this. I created separate Python installs, each for x86_64 and tried to build PyNaCl using crossenv: ```...

I have still been unable to reproduce this, and I can't think of a likely source of the error. This is a complete shot in the dark, but does adding...

It should be added as a parameter when setting up the crossenv helper, something like: ``` @$(RUN) $(PYTHON_NATIVE) -m crossenv --manylinux manylinux2010 $(STAGING_INSTALL_PREFIX)/bin/python$(PKG_VERS_MAJOR_MINOR) $(WORK_DIR)/crossenv/ ```

Wow. Awesome job making a reproducible test case! I think I know what's happening: `numpy` is a build dependency of `matplotlib`, and since it isn't installed when you call `cross-pip...