Benjamin Fogle

It looks like you're using the system version of Python as your build-python. It's highly recommended that you build both build-python and host-python. The version of Python that comes with...

Do you mean that step 3 succeeded? In that case, you should find the files you need in cross_venv/cross/lib/python3.8/site-packages. You can copy them from there to your device to see...

This sounds like a toolchain/cpython issue more than a crossenv issue? When creating the cross environment, would adding `--cxx='arm-frc2020-linux-gnueabi-c++ -pthread'` be a workaround? If that works then that should be...

I need to add that in, certainly. I just need to make sure that that value isn't used internally for anything important, especially from C code. At first glance, it...

I was able to reproduce this, and I might have a clue. It appears that `_multiarray_tests.cpython-38.so` uses a function in `libm.so`, but does not actually declare a dependency on that...

I wouldn't expect it to cause problems (though as @pmp-p said, dynamic linking can be tricky on some systems). For something like Yocto or Buildroot-based distributions, using the target provided...

Looks good. Merging now.

Crossenv is trying to gather information about the builld-python installation from the Makefile that was used to build Python. This is produced after you run `configure` and installed in the...

It actually only sets the environment when Python runs, so you should see them set if you run something like: $ cross-python -c 'import os; print(os.environ["CPATH"])' For numpy specifically, they...

env/cross/{include, lib} aren't used for anything, so it should be safe to symlink things there. Adding a symlink options isn't a bad idea, but first I think I want to...