Make error: cannot convert ‘amqp_table_t’ to ‘amqp_boolean_t’ running on Centos

[akalend]

Make error: cannot convert ‘amqp_table_t’ to ‘amqp_boolean_t’ running on Centos

[martinjkelly]

It seems that the most recent changes in the librabbitmq-c code have caused the issue

alanxz/rabbitmq-c@2340b03

[martinjkelly]

I have found the cause of the issue, details can be found here http://stackoverflow.com/questions/26703443/unable-to-compile-amqpcpp-make-error

[martinjkelly]

Sorry, Didn't mean to close this. The code needs updating to ensure compatibility with the latest changes in the librabbitmq codebase.

[vltr]

@martinjkelly: bumped with the same issue. Newer versions of rabbitmq-c now breaks amqpcpp BUT I wouldn't consider a modification YET because amqpcpp is still compatible with the latest stable release of rabbitmq-c (0.5.2). The instructions of how to use amqpcpp by cloning rabbitmq-c repository directly is the faulty question here (at the time I'm writing). When 0.6 becomes stable, then amqpcpp would require code updates.

[vltr]

@martinjkelly: nevermind. The readme in rabbitmq-c is also wrong, saying the latest stable is indeed v0.6.0 but the link right bellow is to version 0.5.2. What a MESS ... ⚠️

[martinjkelly]

see this SO post on how I worked around it at the time, I haven't looked at it since... http://stackoverflow.com/questions/26703443/unable-to-compile-amqpcpp-make-error.

I've since changed to posting data directly over a socket to my application and bypassing rabbitmq

[vltr]

Yup! I made the same change some hours ago to make it work with 0.6.x :) I
don't think the current author seems keen to continue this project. Maybe
someone could assume it under a new name and add all those changes (from
newer versions of rabbitmq-c to memory leak fixes). Anyone?

On Wed, Feb 25, 2015 at 12:26 PM, Martin Kelly [email protected]
wrote:

see this SO post on how I worked around it at the time, I haven't looked
at it since
http://stackoverflow.com/questions/26703443/unable-to-compile-amqpcpp-make-error

—
Reply to this email directly or view it on GitHub
#38 (comment).