Summary: | sys-libs/libsemanage-2.1.0 - semanageswig_wrap.c:(.text+0x16e16): undefined reference to `PyCObject_Import' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Krzysztof <calypso2k> |
Component: | [OLD] Core system | Assignee: | Sven Vermeulen (RETIRED) <swift> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | selinux |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Complete build.log
The complete build log |
Description
Krzysztof
2012-03-28 08:25:59 UTC
Please attach the entire build log to this bug report. Created attachment 306963 [details]
Complete build.log
This is paravirt OS, if it has any meaning Hmm, my builds don't try Python 3.2, only 3.1. Lemme see if I can reproduce by removing python 3.1 from a system. Nope, can't seem to reproduce. Any chance for you that you can try out the libsemanage-2.1.6 version (it'll ask for ~arch'ing other selinux-related packages as well though)? no problem, as this is xen I can clone VM to test stuff same old, samee old x86_64-pc-linux-gnu-gcc -march=core2 -O2 -pipe -I../include -I/usr/include -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -fPIC -Wl,-O1 -Wl,--as-needed -shared -o python-3.2_selinux.so python-3.2selinuxswig_wrap.lo -L. -lselinux -L/usr/lib64 -lpython3.2 -Wl,-soname,python-3.2_selinux.so,-z,defs python-3.2selinuxswig_wrap.lo: In function `PyInit__selinux': selinuxswig_wrap.c:(.text+0x21aa7): undefined reference to `PyCObject_Import' selinuxswig_wrap.c:(.text+0x21aee): undefined reference to `PyCObject_FromVoidPtr' collect2: ld returned 1 exit status make: *** [python-3.2_selinux.so] Error 1 this time @ sys-libs/libselinux-2.1.9 Do you think there is something wrong with my python installation? Created attachment 307459 [details]
The complete build log
I can confirm this bug. My emerge fails exactly at the same point: x86_64-pc-linux-gnu-gcc -march=native -O2 -pipe -fomit-frame-pointer -I../include -I/usr/include -D_GNU_SOURCE -Wl,-O1 -Wl,--as-needed -shared -o _semanage.so semanageswig_wrap.lo -L. -lsemanage -lpython3.2 -L/usr/lib -Wl,-soname,_semanage.so,-z,defs semanageswig_wrap.lo: In function `PyInit__semanage': semanageswig_wrap.c:(.text+0x1669e): undefined reference to `PyCObject_Import' semanageswig_wrap.c:(.text+0x166e5): undefined reference to `PyCObject_FromVoidPtr' collect2: ld returned 1 exit status make: *** [_semanage.so] Error 1 emake failed I think SOLVED. This is somehow related to [Python] wrapper does not compile with python 3.2 - ID: 3057804. For some reason emerge -uDNv world, with portage timestamp Mon, 02 Apr 2012 00:45:01 +0000, does not pull dev-lang/swig-2.0.4-r1. I had dev-lang/swig-2.0.2. When I did emerge -v swig, it emerged dev-lang/swig-2.0.4-r1 and now everything compiles fine. I supose I update too often ;) The unanswered question is: why emerge didn't pull new swig, while it was available in portage tree? OK, there is no dev-lang/swig entry in /var/lib/portage/world, and sys-libs/libsemanage does not have dependency on swig package, with fixed "[Python] wrapper does not compile with python 3.2 - ID: 3057804". So we're happy and we can close this. Thanks for everyone's time. I'll have it depend on the recent swig version then, thanks Fixed in CVS |