I just downloaded trunk and tried it when I saw your email.

I did make -j8, and the compile did indeed fail, but I didn't feel like
scrolling back to see where the failure was, so I then did "make",
thinking to compile one file at a time to make the failure easier to
see.  ( I do this sometimes. )

But now it's not failing.

< twilight zone music />




On Mon, 2012-06-11 at 14:55 -0500, Steve Huston wrote:
> Did someone see build problems on Linux starting overnight? Same issues on 
> Windows as well.
> 
> -Steve
> 
> -----Original Message-----
> From: CDash [mailto:[email protected]]
> Sent: Sunday, June 10, 2012 9:13 PM
> To: [email protected]
> Subject: FAILED (b=50, w=18): qpid-cpp - trunk - Nightly
> 
> A submission to CDash for the project qpid-cpp has build errors and build 
> warnings.
> You have been identified as one of the authors who have checked in changes 
> that are part of this submission or you are listed in the default contact 
> list.
> 
> Details on the submission can be found at 
> http://www.riverace.com/CDash-1.4.2/buildSummary.php?buildid=2010
> 
> Project: qpid-cpp
> Site: Riverace: RHEL5
> Build Name: trunk
> Build Time: 2012-06-10T21:01:22 EDT
> Type: Nightly
> Errors:50
> Warnings:18
> 
> 
> *Error* (first 5)
> src/qpid/broker/TopicKeyNode.h line sourceline 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: type/value mismatch at 
> argument 2 in template parameter list for 
> ‘template<clsrc/qpid/broker/TopicKeyNode.h line sourceline 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error:   expected a type, got 
> ‘qpid::broker::TopicKeyNode<T>::shared_ptr’
> 
> src/qpid/broker/TopicKeyNode.h line sourceline 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:169: error: template argument 4 is 
> invalid
> 
> src/qpid/broker/TopicKeyNode.h line sourceline 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: ISO C++ forbids 
> declaration of ‘shared_ptr’ with no type
> 
> src/qpid/broker/TopicKeyNode.h line sourceline 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=0&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:171: error: extra qualification 
> ‘qpid::broker::TopicKeyNode<T>::’ on member ‘shared_p
> 
> 
> *Warnings* (first 5)
> src/qpid/broker/TopicKeyNode.h line 211 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:211: note: say ‘typename 
> qpid::broker::TopicKeyNode<T>::shared_ptr’ if a type is meant
> 
> cc1plus: warnings being treated as errors
> 
> /.../cpp/src/qpid/broker/TopicKeyNode.h: At global scope:
> /.../cpp/src/qpid/broker/TopicKeyNode.h: In instantiation of ‘bool 
> qpid::broker::TopicKeyNode<T>::iterateMatchChildren(const 
> qpid::broker::TokenIteratorsrc/qpid/broker/TopicKeyNode.h line 337 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010)
> /.../cpp/src/qpid/broker/TopicKeyNode.h:337: warning: unused parameter 
> ‘iter’
> 
> include/qpid/messaging/Duration.h line 53 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010)
> /.../cpp/include/qpid/messaging/Duration.h:53: Warning(378): operator!= 
> ignored
> 
> include/qmf/engine/ConnectionSettings.h line 110 
> (http://www.riverace.com/CDash-1.4.2/viewBuildError.php?type=1&buildid=2010)
> /.../cpp/include/qmf/engine/ConnectionSettings.h:110: Warning(472): 
> Overloaded transportTcp(qmf::engine::ConnectionSettings *self
> 
> -CDash on www.riverace.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]

Reply via email to