On Tue, Nov 30, 2010 at 6:10 PM, Mr Dash Four
<mr.dash.f...@googlemail.com> wrote:
>
>> 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 'hello'
> program to test it:
>
> #include <stdio.h>
> #include <event-config.h>
>
> int main(void)
> {
> printf("Size of long is %u\n",_EVENT_SIZEOF_LONG);
> return 0;
> }
>
> [z...@test1 ~]$ gcc -o hello hello.c
> [z...@test1 ~]$ ./hello
> Size of long is 8
>
> [z...@xp1 ~]$ gcc -o hello -m32 hello.c
> [z...@xp1 ~]$ ./hello
> Size of long is 4
>
>
> So, it works. There is one thing I am not 100% sure though - at the very top
> of both -32 and -64 versions of event-config.h there is the following:
>
> /* event-config.h
> * Generated by autoconf; post-processed by libevent.
> * Do not edit this file.
> * Do not rely on macros in this file existing in later versions.
> */
>
>
> Does this mean that this file could be changed by autoconf then? Because if
> that is the case the new-look event-config.h will be absolutely screwed and
> there is no point on doing anything as the next time autoconf decides to
> change that file all will be lost and it will all be back to square one!
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.
--
Nick
***********************************************************************
To unsubscribe, send an e-mail to majord...@freehaven.net with
unsubscribe libevent-users in the body.
