The CI job (https://builds.apache.org/job/Qpid-Java-Cpp-Test/) still
doesn't seem to be very happy. Is there anything needing done to cleanup
from the previous issue?

<snip>
make[1]: Entering directory `<
https://builds.apache.org/job/Qpid-Java-Cpp-Test/ws/trunk/qpid/cpp/managementgen
'>
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `<
https://builds.apache.org/job/Qpid-Java-Cpp-Test/ws/trunk/qpid/cpp/managementgen
'>
Making all in etc
make[1]: Entering directory `<
https://builds.apache.org/job/Qpid-Java-Cpp-Test/ws/trunk/qpid/cpp/etc'>
sed "s|!!sysconfdir!!|/usr/local/
etc|;s|!!sbindir!!|/usr/local/sbin|;s|!!bindir!!|/usr/local/bin|"
qpidd.in> qpidd
sed
"s|!!sysconfdir!!|/usr/local/etc|;s|!!sbindir!!|/usr/local/sbin|;s|!!bindir!!|/usr/local/bin|"
qpidd-primary.in > qpidd-primary
make[1]: *** No rule to make target `qpidd.service', needed by `all-am'.
 Stop.
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory `<
https://builds.apache.org/job/Qpid-Java-Cpp-Test/ws/trunk/qpid/cpp/etc'>
make: *** [all-recursive] Error 1



On 28 November 2012 15:07, Andrew Stitcher <[email protected]> wrote:

> On Tue, 2012-11-27 at 13:32 -0500, Darryl L. Pierce wrote:
> > I've pushed the new Qpid Perl bindings to master today. This newer
> > binding layer more closely matches what's defined in the C++ layer.
> >
> > The namespace for each class is qpid::messaging and the class names are
> > a 1:1 match to what's in C++. The method names as well, with underscore
> > case replacing camel case, which is more intuitive for dynamic
> > languages.
> >
> > Also updated are the Perl examples, which now use the updated APIs.
>
> Can I point out that somewhere in the changes you just made you broke
> the build for the bindings for both the cmake and autotools builds. I
> checked in a fix for this now, could you be more careful next time?
>
> (I will admit that this is pot calling kettle black, but still...)
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to