Summary: | dev-python/pyxattr fails install on crossdev: pyport.h:886:2: error: #error "LONG_BIT definition appears wrong for platform (bad gcc/glibc config?)." | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kent Fredric (IRC: kent\n) (RETIRED) <kentnl> |
Component: | Current packages | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | adborden, alexey+gentoo, email, herrtimson, necktwi, python, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | cross-einfo |
Description
Kent Fredric (IRC: kent\n) (RETIRED)
![]() Cross-compiling python packages is not generally expected to work. In this case, the native Python.h file from /usr/lib/python2.7 is being used; for the cross compile to work, distutils would have to be smart enough to use the python headers installed in the sysroot environment. I have the same problem, and is not that I want to install python in my crossdev toolchain, it that some packages demand it. Is there any workaround to it? (In reply to Eduardo Barreto Alexandre from comment #2) > Is there any workaround to it? Modify your USE flags so that pyxattr is not pulled into the depgraph. same error while merging pyblake (dependency to portage). any use flag mask to avoid pyblake as well? This occurs with dev-python/pypax as well. Only way around it is to remove sys-apps/elfix from hardened profile package world file. Ebuild now uses PEP517 and mgorny recently added cross-compile support to gpep517. This should work now. |