I have a kqueue-based poller that I worked on several months ago.  The thread 
local implementation I put together for OS X is a quick hack and definitely 
needs to be redone.  See https://github.com/ncdc/qpid/tree/mac.

Andy

On Jul 19, 2012, at 3:03 PM, Steve Huston wrote:

> No, those are related to setting up integer types definitionsÅ  follow the
> path through Broker.h and look for something including integer_types.h or
> something similar. Look through there to see if there's a missing platform
> file or what it's looking for.
> 
> You will run into other problems past thisÅ  I'm not sure the poller has
> been tried on OS X and that's probably the biggest effort required to
> start testing the port.
> 
> -Steve
> 
> On 7/19/12 3:18 PM, "aparikh" <[email protected]> wrote:
> 
>> Thanks.. 
>> I installed boost via homebrew and it is not throwing error about missing
>> headers.. However, getting below error on make..Is this related to gcc
>> thread local support ?
>> 
>> 
>> 
>> In file included from qpid/ha/Backup.cpp:29:
>> ./qpid/broker/Broker.h:115: error: 'uint' does not name a type
>> ./qpid/broker/Broker.h:123: error: 'uint' does not name a type
>> ./qpid/broker/Broker.h:124: error: 'uint' does not name a type
>> In file included from qpid/ha/Backup.cpp:31:
>> ./qpid/broker/Link.h:77: error: 'uint' does not name a type
>> ./qpid/broker/Link.h:128: error: 'uint' does not name a type
>> make[3]: *** [qpid/ha/Backup.lo] Error 1
>> make[2]: *** [all-recursive] Error 1
>> make[1]: *** [all] Error 2
>> make: *** [all-recursive] Error 1
>> 
>> 
>> --
>> View this message in context:
>> http://qpid.2158936.n2.nabble.com/Qpid-C-broker-install-on-Mac-Lion-tp7579
>> 931p7579940.html
>> Sent from the Apache Qpid users mailing list archive at Nabble.com.
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to