This seems to be the problem:
http://code.google.com/p/pyevent/issues/detail?id=23
Fix is in SNV: see instructions at bottom of thread there.
On 29/09/2010, at 10:10 AM, Mark Nottingham wrote:
> In a fresh Fedora 13 install (x86_64), after yum installing pyevent, I get:
>
> ---8<---
>
> [...]
> Running Transaction
> Installing : libevent-devel-1.4.13-1.fc13.x86_64
> 1/1
>
> Installed:
> libevent-devel.x86_64 0:1.4.13-1.fc13
>
>
> Complete!
> qa2:~> python
> Python 2.6.4 (r264:75706, Jun 4 2010, 18:20:31)
> [GCC 4.4.4 20100503 (Red Hat 4.4.4-2)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import event
> Traceback (most recent call last):
> File "", line 1, in
> ImportError: /usr/lib64/python2.6/site-packages/event.so: undefined symbol:
> event_sigcb
>>>>
> qa2:~> ldd /usr/lib64/python2.6/site-packages/event.so
>linux-vdso.so.1 => (0x7fffad9fb000)
>libevent-1.4.so.2 => /usr/lib64/libevent-1.4.so.2 (0x7f236996f000)
>libpython2.6.so.1.0 => /usr/lib64/libpython2.6.so.1.0
> (0x7f23695b7000)
>libpthread.so.0 => /lib64/libpthread.so.0 (0x7f236939a000)
>libc.so.6 => /lib64/libc.so.6 (0x7f236901b000)
>libnsl.so.1 => /lib64/libnsl.so.1 (0x7f2368e02000)
>librt.so.1 => /lib64/librt.so.1 (0x7f2368bf9000)
>libresolv.so.2 => /lib64/libresolv.so.2 (0x7f23689df000)
>libdl.so.2 => /lib64/libdl.so.2 (0x7f23687db000)
> libutil.so.1 => /lib64/libutil.so.1 (0x00007f23685d7000)
>libm.so.6 => /lib64/libm.so.6 (0x7f2368353000)
>/lib64/ld-linux-x86-64.so.2 (0x00366c60)
>
> --->8---
>
>
> --
> Mark Nottingham http://www.mnot.net/
>
--
Mark Nottingham http://www.mnot.net/
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
