| Summary: | dev-lang/python-3.12.4_p2 refuses to cross-emerge into an Armv7-A target | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Roland Metivier <metivier.roland> |
| Component: | Current packages | Assignee: | Python Gentoo Team <python> |
| Status: | UNCONFIRMED --- | ||
| Severity: | normal | CC: | chewi, dave, metivier.roland |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | emerge --info, emerge -pqv, and Python's build.log concatenated | ||
dev-lang/python builds 2 copies of python: one for CBUILD and one for CHOST. Do you somehow not have libffi installed for CBUILD? (In reply to Mike Gilbert from comment #1) > dev-lang/python builds 2 copies of python: one for CBUILD and one for CHOST. > > Do you somehow not have libffi installed for CBUILD? libffi 3.4.4-r4 is installed on CBUILD. I have this problem as well, compiling with crossdev for powerpc. I think it may be specifically a problem with a 64-bit build host and a 32-bit target. The host has /usr/lib64/libffi/include/ffi.h, but Python believes it lives in /usr/lib/libffi/include instead. Can confirm that symlinking /usr/lib/libffi -> ../lib/libffi works as a temporary solution, and allows Python to cross-build. Woops I meant /usr/lib/libffi -> ../lib64/libffi |
Created attachment 898382 [details] emerge --info, emerge -pqv, and Python's build.log concatenated Using target profile "default/linux/arm/23.0/split-usr/armv7a_hf" and emerging @system. Host has profile "default/linux/amd64/23.0/desktop/systemd". The crossdev environment is trying to pull in the host's libffi from the wrong location, as seen in the log files. This might be an issue with the Python ebuild.