➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author steve.dower
Recipients Alex.Willmer, bill9889, doko, iliis, ned.deily, steve.dower, wscullin, xdegaye
Date 2020-03-20.20:22:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1584735763.75.0.775931132252.issue22699@roundup.psfhosted.org>
In-reply-to
Content 
> 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?
History
Date User Action Args
2020-03-20 20:22:43steve.dowersetrecipients: + steve.dower, doko, ned.deily, xdegaye, Alex.Willmer, bill9889, wscullin, iliis
2020-03-20 20:22:43steve.dowersetmessageid: <1584735763.75.0.775931132252.issue22699@roundup.psfhosted.org>
2020-03-20 20:22:43steve.dowerlinkissue22699 messages
2020-03-20 20:22:43steve.dowercreate