You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Keith W <ke...@gmail.com> on 2011/11/11 09:27:49 UTC

Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found

Hi

I'm running into problems building cpp on trunk this morning.  The
configure step is failing.  Is there a new dependency or some extra
commands I need to run?  I'm on RHEL 5.3 but I notice the same
failiure occuring on the Jenkins ubuntu slaves.

cd qpid/cpp
./bootstrap;
./configure

cheers Keith.

(snip)
config.status: error: cannot find input file: src/qmf2.pc.in
 cd . && /bin/sh
/home/keith/src/apache/qpid/qpid/cpp/build-aux/missing --run
automake-1.9 --foreign
configure.ac:551: required file `src/qmf2.pc.in' not found
make: *** [Makefile.in] Error 1
(snip)

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


RE: Remove autotools? [Was: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found]

Posted by Steve Huston <sh...@riverace.com>.
+20 :-)

> -----Original Message-----
> From: Cliff Jansen [mailto:cliffjansen@gmail.com]
> Sent: Friday, November 11, 2011 12:02 PM
> To: dev@qpid.apache.org
> Subject: Re: Remove autotools? [Was: Problems building trunk cpp broker
> since this morning - `src/qmf2.pc.in' not found]
>
> +1
>
> An additional sub-task would be to rework the separate powershell and sh
> scripts within cmake/ctest to a single base (python is a likely
candidate), so
> that contributers don't need to wear multiple hats.
>
> On Fri, Nov 11, 2011 at 7:53 AM, Andrew Stitcher <as...@redhat.com>
> wrote:
> > On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
> >> This kind of thing seems like a good reason to add a CMake build
> >> project to Jenkins (or, you know, just have 1 build system :p) in
> >> addition to the autotools build Keith set up. Any takers?
> >
> > Personally I go for the 1 build system - Cmake.
> >
> > At present Cmake is very nearly at parity with autotools (given the
> > recent work I checked in from Jan-Marek Glogowski) and I'd say it
> > would be feasible (given the available time) to remove autotools and
> > shift to cmake in the 0.16 time frame.
> >
> > I think the only remaining work is to make the tests on cmake be at
> > parity with autotools.
> >
> > [There's also tidying work we should do, because neither of the build
> > systems is very pretty or very maintainable at this point, but having
> > just one would help a lot]
> >
> > Andrew
> >
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project:      http://qpid.apache.org
> > Use/Interact: mailto:dev-subscribe@qpid.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Re: Remove autotools? [Was: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found]

Posted by Cliff Jansen <cl...@gmail.com>.
+1

An additional sub-task would be to rework the separate powershell and
sh scripts within cmake/ctest to a single base (python is a likely
candidate), so that contributers don't need to wear multiple hats.

On Fri, Nov 11, 2011 at 7:53 AM, Andrew Stitcher <as...@redhat.com> wrote:
> On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
>> This kind of thing seems like a good reason to add a CMake build
>> project to Jenkins (or, you know, just have 1 build system :p) in
>> addition to the autotools build Keith set up. Any takers?
>
> Personally I go for the 1 build system - Cmake.
>
> At present Cmake is very nearly at parity with autotools (given the
> recent work I checked in from Jan-Marek Glogowski) and I'd say it would
> be feasible (given the available time) to remove autotools and shift to
> cmake in the 0.16 time frame.
>
> I think the only remaining work is to make the tests on cmake be at
> parity with autotools.
>
> [There's also tidying work we should do, because neither of the build
> systems is very pretty or very maintainable at this point, but having
> just one would help a lot]
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Re: Remove autotools? [Was: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found]

Posted by Alan Conway <ac...@redhat.com>.
+1

On 11/11/2011 10:53 AM, Andrew Stitcher wrote:
> On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
>> This kind of thing seems like a good reason to add a CMake build
>> project to Jenkins (or, you know, just have 1 build system :p) in
>> addition to the autotools build Keith set up. Any takers?
>
> Personally I go for the 1 build system - Cmake.
>
> At present Cmake is very nearly at parity with autotools (given the
> recent work I checked in from Jan-Marek Glogowski) and I'd say it would
> be feasible (given the available time) to remove autotools and shift to
> cmake in the 0.16 time frame.
>
> I think the only remaining work is to make the tests on cmake be at
> parity with autotools.
>
> [There's also tidying work we should do, because neither of the build
> systems is very pretty or very maintainable at this point, but having
> just one would help a lot]
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Remove autotools? [Was: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found]

Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2011-11-11 at 15:24 +0000, Robbie Gemmell wrote:
> This kind of thing seems like a good reason to add a CMake build
> project to Jenkins (or, you know, just have 1 build system :p) in
> addition to the autotools build Keith set up. Any takers?

Personally I go for the 1 build system - Cmake.

At present Cmake is very nearly at parity with autotools (given the
recent work I checked in from Jan-Marek Glogowski) and I'd say it would
be feasible (given the available time) to remove autotools and shift to
cmake in the 0.16 time frame.

I think the only remaining work is to make the tests on cmake be at
parity with autotools.

[There's also tidying work we should do, because neither of the build
systems is very pretty or very maintainable at this point, but having
just one would help a lot]

Andrew



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


Re: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found

Posted by Robbie Gemmell <ro...@gmail.com>.
This kind of thing seems like a good reason to add a CMake build
project to Jenkins (or, you know, just have 1 build system :p) in
addition to the autotools build Keith set up. Any takers?

On 11 November 2011 14:52, Andrew Stitcher <as...@redhat.com> wrote:
> On Fri, 2011-11-11 at 08:32 -0600, Steve Huston wrote:
>> The cmake build failed last night as well... couldn't configure:
>>
>> CMake Error: File /qpidbuilds/trunk/qpid/cpp/src/qmf2.pc.in does not
>> exist.
>> CMake Error at src/CMakeLists.txt:1369 (configure_file):
>>   configure_file Problem configuring file
>
> Mea Culpa - I missed adding the necessary new file!
>
> Andrew
>
>
>
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org
>
>

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


RE: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found

Posted by Andrew Stitcher <as...@redhat.com>.
On Fri, 2011-11-11 at 08:32 -0600, Steve Huston wrote:
> The cmake build failed last night as well... couldn't configure:
> 
> CMake Error: File /qpidbuilds/trunk/qpid/cpp/src/qmf2.pc.in does not
> exist.
> CMake Error at src/CMakeLists.txt:1369 (configure_file):
>   configure_file Problem configuring file

Mea Culpa - I missed adding the necessary new file!

Andrew



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org


RE: Problems building trunk cpp broker since this morning - `src/qmf2.pc.in' not found

Posted by Steve Huston <sh...@riverace.com>.
The cmake build failed last night as well... couldn't configure:

CMake Error: File /qpidbuilds/trunk/qpid/cpp/src/qmf2.pc.in does not
exist.
CMake Error at src/CMakeLists.txt:1369 (configure_file):
  configure_file Problem configuring file

> -----Original Message-----
> From: Keith W [mailto:keith.wall@gmail.com]
> Sent: Friday, November 11, 2011 3:28 AM
> To: dev@qpid.apache.org
> Subject: Problems building trunk cpp broker since this morning -
> `src/qmf2.pc.in' not found
> 
> Hi
> 
> I'm running into problems building cpp on trunk this morning.  The
configure
> step is failing.  Is there a new dependency or some extra commands I
need
> to run?  I'm on RHEL 5.3 but I notice the same failiure occuring on the
Jenkins
> ubuntu slaves.
> 
> cd qpid/cpp
> ./bootstrap;
> ./configure
> 
> cheers Keith.
> 
> (snip)
> config.status: error: cannot find input file: src/qmf2.pc.in  cd . &&
/bin/sh
> /home/keith/src/apache/qpid/qpid/cpp/build-aux/missing --run
> automake-1.9 --foreign
> configure.ac:551: required file `src/qmf2.pc.in' not found
> make: *** [Makefile.in] Error 1
> (snip)
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:dev-subscribe@qpid.apache.org


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org