[zeromq-dev] compiling for HP-UX

AJ Lewis aj.lewis at quantum.com
Wed Sep 26 23:20:04 CEST 2012

On Wed, Sep 26, 2012 at 01:40:13PM -0700, brian jackson wrote:
> On Wednesday 26 September 2012 12:37:41 AJ Lewis wrote:
> > Yeah, you need this fix
> > (https://github.com/zeromq/zeromq3-x/commit/14da52c3aad5fa83cb167e2bf49200e072a61d1e)
> > applied to 3.2.0-rc1 to get it building on HPUX.  I don't think
> > there's been an official 3.2 release since that fix went into git.
> patch applied, but still getting the original error:
>   CXX    libzmq_la-address.lo "tcp_address.hpp", line 42: error
>   #2020: identifier "sockaddr" is undefined tcp_address_t (const
>   sockaddr *sa, socklen_t sa_len);

Odd...It almost seems like you're missing header files, but I don't
know HPUX well enough to say for sure.

I am using a newer version of aCC:
aCC: HP C/aC++ B3910B A.06.25 [Nov 30 2009]

struct sockaddr should be defined in sys/socket.h, but I guess in
that case it's just calling it sockaddr - shouldn't that be 'struct
sockaddr'?  Not sure why that's working on my system...
> > There's a fix for HPUX in zeromq-2x
> > (https://github.com/zeromq/zeromq2-x/commit/8123b18284b1dadf4a72b7d6e644471539239282)
> > that was needed to get 2-x compiling - not sure if that's in the
> > latest 2.2 release or not...
> these fixes did make it into the 2.2.0, but they don't help.  In fact I have to back out one as it complains about not being able to locate "gethrtime"
> thanks,
> brian
> -- 
> Brian Jackson
> Oracle - PDIT - DevOps

AJ Lewis
Software Engineer
Quantum Corporation

Work:    651 688-4346
email:   aj.lewis at quantum.com

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.

More information about the zeromq-dev mailing list