Pieter,

The related code doesn't exist in 3.1. The patch is to be applied to 2.1 
and 3.0.

Martin

On 11/09/2011 12:13 AM, AJ Lewis wrote:
> Decided to just submit the patch - see attached.  It's also in my pull
> request...
>
> Thanks,
> AJ
>
> On Tue, Nov 08, 2011 at 12:21:47PM -0600, AJ Lewis wrote:
>> On Mon, Nov 07, 2011 at 10:11:44PM +0100, Martin Sustrik wrote:
>>> On 11/07/2011 10:05 PM, AJ Lewis wrote:
>>>
>>>> $ gcc --version
>>>> gcc (GCC) 4.2.0
>>>> Copyright (C) 2007 Free Software Foundation, Inc.
>>>> This is free software; see the source for copying conditions.  There is NO
>>>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>>>>
>>>> Maybe I need to get a newer one installed - I've had other issues with
>>>> this one as well...(gcc actually segfaults when trying to compile google
>>>> protocol buffers IIRC)
>>>
>>> I am using gcc-4.4.3, however, we should make compilation with 4.2.0 work...
>>>
>>> What about adding the forward declaration as mentioned before *and*
>>> changing the two offending occurences of "class msg_t" to
>>> "zmq::msg_t"?
>>
>> This appears to work!  Should I submit a patch for this, or do you want
>> to take care of it?  I just had to change i_enginte.hpp.
>>
>> --
>> AJ Lewis
>> Software Engineer
>> Quantum Corporation
>>
>> Mobile:  612 860-8068
>> Work:    651 688-4346
>> YahooIM: vortechs2000
>> AIM:     v0r73chz
>> MSN:     [email protected]
>> email:   [email protected]
>>
>> ----------------------------------------------------------------------
>> The information contained in this transmission may be confidential. Any 
>> disclosure, copying, or further distribution of confidential information is 
>> not permitted unless such privilege is explicitly granted in writing by 
>> Quantum. Quantum reserves the right to have electronic communications, 
>> including email and attachments, sent across its networks filtered through 
>> anti virus and spam software programs and retain such messages in order to 
>> comply with applicable data security and retention requirements. Quantum is 
>> not responsible for the proper and complete transmission of the substance of 
>> this communication or for any delay in its receipt.
>> _______________________________________________
>> zeromq-dev mailing list
>> [email protected]
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>

_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to