Steve Dower <steve.do...@python.org> added the comment:
> the multiarch approach allows you to install libraries and headers for many > architectures in the same installation/chroot That makes sense, but I'm not using it. So presumably I've added a configure option that I didn't need (either "--host=x86_64-my-linux" or "--build=x86_64"). I'm building against a Yocto SDK (like described at https://www.yoctoproject.org/docs/2.1/sdk-manual/sdk-manual.html#sdk-installing-the-sdk), and the --host option identifies the sysroot. When I add just --host, I also have to add --build, and IIRC only x86_64 worked. Could that have enabled the multiarch settings? Or it is always enabled because I'm building on an Ubuntu VM? ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue22699> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
