building '_ctypes' extension armv4tl-softfloat-linux-gnueabi-gcc -fPIC -DNDEBUG -march=armv4t -mtune=arm920t -Os -pipe -Wa,--noexecstack -I/usr/lib64/libffi-3.0.8/include -I. -I/var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4/./Include -I/usr/armv4tl-softfloat-linux-gnueabi/usr/include -I. -IInclude -I./Include -I/var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4/Include -I/var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4 -c /var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4/Modules/_ctypes/_ctypes.c -o build/temp.linux-x86_64-2.6/var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4/Modules/_ctypes/_ctypes.o In file included from /usr/lib64/libffi-3.0.8/include/ffi.h:66, from /var/tmp/portage/dev-lang/python-2.6.4/work/Python-2.6.4/Modules/_ctypes/_ctypes.c:112: /usr/lib64/libffi-3.0.8/include/ffitarget.h:67: error: ‘FFI_DEFAULT_ABI’ undeclared here (not in a function) Failed to find the necessary bits to build these modules: _bsddb _multiprocessing _tkinter bsddb185 dbm dl gdbm imageop sunaudiodev To find the necessary bits, look in setup.py in detect_modules() for the module's name. Failed to build these modules: _ctypes Reproducible: Always Steps to Reproduce:
Created attachment 214676 [details] build.log
Created attachment 214678 [details, diff] 10_all_use_external_libffi.patch.patch This is a patch for the gentoo patch that broke crosscompile to use the right pkg-config instead of the native one
(In reply to comment #2) > Created an attachment (id=214678) [details] > 10_all_use_external_libffi.patch.patch > > This is a patch for the gentoo patch that broke crosscompile to use the right > pkg-config instead of the native one > this did not fix the problem for me.
(In reply to comment #3) > this did not fix the problem for me. How did you use the patch? I don't think you can use it directly from portage, at least I was not able to do it. You need to patch a file that is inside /usr/portage/distfiles/python-gentoo-patches-2.6.4.tar.bz2, the problem is that if you patch the file and recreate the archive it will not match the manifest so portage will redownload the original. Maybe there is an option for emerge not to check the digest / filesize but I did not find one that works in this case.
(In reply to comment #4) > (In reply to comment #3) > > this did not fix the problem for me. > How did you use the patch? I don't think you can use it directly from portage, > at least I was not able to do it. You need to patch a file that is inside > /usr/portage/distfiles/python-gentoo-patches-2.6.4.tar.bz2, the problem is that > if you patch the file and recreate the archive it will not match the manifest > so portage will redownload the original. Maybe there is an option for emerge > not to check the digest / filesize but I did not find one that works in this > case. > I applied the patch in a rather crude manner. I ctrl+Z 'd the emerge and patched patch manually before resuming with fg
Created attachment 217283 [details] build log I stand corrected, I have no idea what i did the first time, but it does fix the problem you were trying to address. now I'm left with this tho. grrr.....
(In reply to comment #6) > Created an attachment (id=217283) [details] > build log > > I stand corrected, I have no idea what i did the first time, but it does fix > the problem you were trying to address. > > now I'm left with this tho. grrr..... > That's an entirelly different issue, related to unicode support, you should log a different bug for that. Also, if you want to workaround it for now maybe disabling the test FEATURE / USE will do.
Fixed in 2.6.4-r1 and 3.1.1-r1.
> That's an entirelly different issue, related to unicode support, you should log > a different bug for that. Also, if you want to workaround it for now maybe > disabling the test FEATURE / USE will do. > thanks, but there's no "test" in my FEATURES or USE according to "xmerge --root <mybuildroot> --info" will check bugs and file another report :(
