Looks good, thanks!
Brian
On 7/14/11 1:12 AM, "Ralph Castain" wrote:
>Should be fixed in r24902 - let me know.
>
>
>On Jul 12, 2011, at 4:30 PM, Barrett, Brian W wrote:
>
>> On 7/12/11 4:21 PM, "Ralph Castain" wrote:
>>
>>> On Jul 12, 2011, at 12:29 PM, Barrett, Brian W wrote:
>>>
On 7/
Should be fixed in r24902 - let me know.
On Jul 12, 2011, at 4:30 PM, Barrett, Brian W wrote:
> On 7/12/11 4:21 PM, "Ralph Castain" wrote:
>
>> On Jul 12, 2011, at 12:29 PM, Barrett, Brian W wrote:
>>
>>> On 7/11/11 4:31 PM, "Ralph Castain" wrote:
>>>
On Jul 11, 2011, at 2:51 PM, Barre
On 7/12/11 4:21 PM, "Ralph Castain" wrote:
>On Jul 12, 2011, at 12:29 PM, Barrett, Brian W wrote:
>
>> On 7/11/11 4:31 PM, "Ralph Castain" wrote:
>>
>>> On Jul 11, 2011, at 2:51 PM, Barrett, Brian W wrote:
>>>
Hi all -
When libevent was made its own component last fall, it appe
On Jul 12, 2011, at 12:29 PM, Barrett, Brian W wrote:
> On 7/11/11 4:31 PM, "Ralph Castain" wrote:
>
>> On Jul 11, 2011, at 2:51 PM, Barrett, Brian W wrote:
>>
>>> Hi all -
>>>
>>> When libevent was made its own component last fall, it appears that the
>>> function renames and visibility set
On 7/11/11 4:31 PM, "Ralph Castain" wrote:
>On Jul 11, 2011, at 2:51 PM, Barrett, Brian W wrote:
>
>> Hi all -
>>
>> When libevent was made its own component last fall, it appears that the
>> function renames and visibility settings were lost. This is proving
>> rather problematic for a projec
On Jul 11, 2011, at 2:51 PM, Barrett, Brian W wrote:
> Hi all -
>
> When libevent was made its own component last fall, it appears that the
> function renames and visibility settings were lost. This is proving
> rather problematic for a project I'm trying to get running with the trunk
> which
Hi all -
When libevent was made its own component last fall, it appears that the
function renames and visibility settings were lost. This is proving
rather problematic for a project I'm trying to get running with the trunk
which uses libev (which provides a libevent compatibility layer). It
wor
