Hi,

RC4 looking much better, but QPID-4724 doesn't seem to have been included so 
doesn't build until patch applied. If its too late, should it be added to the 
release notes instead to manually apply?

Cheers,

Jimmy
  
----- Original Message -----
From: Darryl L. Pierce
Sent: 05/13/13 09:44 PM
To: [email protected]
Subject: Re: Remaining perl bindings issues in RC3
 On Fri, May 10, 2013 at 05:42:10PM +0200, Jimmy Jones wrote:
> Hi,
> 
> Done some more testing of RC3, and unfortunatly its still not possible to 
> build the perl bindings. The outstanding issues:
> 
> * QPID-4781 cmake build of perl bindings fails in RC2 - confusion between 
> cqpid_perl.so and libcqpid_perl.so in install

This is fixed, tested and pushed to master. I put in a request for
inclusion for it today.

> * QPID-4724 qpid-cpp-0.22-rc1 RHEL6 cmake issues - approved for 0.22 but not 
> in RC3

Sorry, thought this was pulled into the 0.22 branch. It's there now.

> * QPID-4828 qpid-cpp-0.22-rc3 RHEL5 cmake issues - same as the above, but for 
> RHEL5 - doesn't auto detect perl paths

Hrm, so this really isn't a build issue per se; i.e., there's nothing we
can do in our build environment to overcome the issue? Should this be
included as a release note for RHEL5 builds?

> * QPID-4770 Perl bindings don't build from qpid-0.22-rc2.tar.gz - an automake 
> failure, i guess not so important as deprected
> * QPID-4719 Problem building perl bindings from qpid 0.22 RC1 tarball - fixup 
> to Makefile.am EXTRA_DIST to include missing files, not approved for 0.22?

This last one has an outstanding request for inclusion on it.

Justin: Can you take a look at the two RFIs? 

> I'd say if the first two are the most important for 0.22, without them the 
> bindings aren't usable on RHEL5/6 in my testing.

-- 
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/ 

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

Reply via email to