[Libevent-users] evdns.c error (libevent 2.0.10)

2011-04-16 Thread Mr Dash Four
I am getting the following error message in syslog: Error from libevent: evdns.c:1360: Assertion req != port->pending_replies failed in server_port_flush I do not know what that error means, but it happens when I get disconnected and the application which uses the network interface (tor) can

Re: [Libevent-users] can libevent-devel for x86_64 and i686 coexist on a x86_64 machine?

2011-01-21 Thread Mr Dash Four
Bug submitted to Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=658858 Even though I submitted this bug to Fedora almost two whole months ago and proposed a (pretty-decent, in my view) solution in that submission nothing has been done - it seems that nobody's bothered! *

Re: [Libevent-users] can libevent-devel for x86_64 and i686 coexist on a x86_64 machine?

2010-12-01 Thread Mr Dash Four
It's generated by autoconf *as part of the build process for Libevent*. If you build a new libevent with --prefix=/usr and do "sudo make install" on it, then you will overwrite /usr/include/event2/event-config.h. But if you're using a packaging system, then you shouldn't ever do that. Ah, r

Re: [Libevent-users] can libevent-devel for x86_64 and i686 coexist on a x86_64 machine?

2010-11-30 Thread Mr Dash Four
It's generated by autoconf *as part of the build process for Libevent*. If you build a new libevent with --prefix=/usr and do "sudo make install" on it, then you will overwrite /usr/include/event2/event-config.h. But if you're using a packaging system, then you shouldn't ever do that. Ah, r

Re: [Libevent-users] can libevent-devel for x86_64 and i686 coexist on a x86_64 machine?

2010-11-30 Thread Mr Dash Four
That's plausible; packagers should probably indeed do something like this; I hope that the package maintainer accepts it or something likes it. Tested it and it works to absolute perfection! I've done the changes exactly as I listed them in my previous post and have also created a small 'he