OK - so the build works on my other machine 32bit Ubuntu 9.10 So the failure seems to be specific to the machine I tried the build on:
[...@frumpy ~]$ uname -a Linux frumpy 2.6.30.9-102.fc11.x86_64 #1 SMP Fri Dec 4 00:18:53 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Looking at the differences in the generated Makefiles, there's a lot of stuff in the "broken" one which is commented out in the "working" one: 97,101c97,101 < #qmfengine_la_DEPENDENCIES = \ < # $(am__DEPENDENCIES_1) \ < # $(top_builddir)/src/libqmfengine.la < #nodist_qmfengine_la_OBJECTS = \ < # qmfengine_la-qmfengine.lo --- > qmfengine_la_DEPENDENCIES = \ > $(am__DEPENDENCIES_1) \ > $(top_builddir)/src/libqmfengine.la > nodist_qmfengine_la_OBJECTS = \ > qmfengine_la-qmfengine.lo 106c106 < #am_qmfengine_la_rpath = -rpath $(rubylibarchdir) --- > am_qmfengine_la_rpath = -rpath $(rubylibarchdir) 284,295c284,295 < #INCLUDES = -I$(top_srcdir)/include -I$(top_builddir)/include -I$(top_srcdir)/src -I$(top_builddir)/src < #EXTRA_DIST = ruby.i < #BUILT_SOURCES = qmfengine.cpp < #rubylibdir = $(RUBY_LIB) < #dist_rubylib_DATA = qmf.rb < #rubylibarchdir = $(RUBY_LIB_ARCH) < #rubylibarch_LTLIBRARIES = qmfengine.la < #qmfengine_la_LDFLAGS = -avoid-version -module -shrext ".$(RUBY_DLEXT)" < #qmfengine_la_LIBADD = $(RUBY_LIBS) -L$(top_builddir)/src/.libs -lqpidclient $(top_builddir)/src/libqmfengine.la < #qmfengine_la_CXXFLAGS = $(INCLUDES) -I$(RUBY_INC) -I$(RUBY_INC_ARCH) < #nodist_qmfengine_la_SOURCES = qmfengine.cpp < #CLEANFILES = qmfengine.cpp --- > INCLUDES = -I$(top_srcdir)/include -I$(top_builddir)/include -I$(top_srcdir)/src -I$(top_builddir)/src > EXTRA_DIST = ruby.i > BUILT_SOURCES = qmfengine.cpp > rubylibdir = $(RUBY_LIB) > dist_rubylib_DATA = qmf.rb > rubylibarchdir = $(RUBY_LIB_ARCH) > rubylibarch_LTLIBRARIES = qmfengine.la > qmfengine_la_LDFLAGS = -avoid-version -module -shrext ".$(RUBY_DLEXT)" > qmfengine_la_LIBADD = $(RUBY_LIBS) -L$(top_builddir)/src/.libs -lqpidclient $(top_builddir)/src/libqmfengine.la > qmfengine_la_CXXFLAGS = $(INCLUDES) -I$(RUBY_INC) -I$(RUBY_INC_ARCH) > nodist_qmfengine_la_SOURCES = qmfengine.cpp > CLEANFILES = qmfengine.cpp 640,641c640,641 < #qmfengine.cpp: $(srcdir)/ruby.i $(srcdir)/../qmfengine.i < # $(SWIG) -ruby -c++ -Wall -I/usr/include $(INCLUDES) $(QPID_CXXFLAGS) -o qmfengine.cpp $(srcdir)/ruby.i --- > qmfengine.cpp: $(srcdir)/ruby.i $(srcdir)/../qmfengine.i > $(SWIG) -ruby -c++ -Wall -I/usr/include $(INCLUDES) $(QPID_CXXFLAGS) -o qmfengine.cpp $(srcdir)/ruby.i Hope this helps, Rob 2009/12/30 Robert Godfrey <[email protected]> > Should I be able to just download the build the > qpid-cpp-0.6rc2.tar.gz<http://qpid.apache.org/dist/qpid-0.6rc2/qpid-cpp-0.6rc2.tar.gz>in > isolation? > > When I download this and try to configure then make the broker I get the > following error: > > Making all in ruby > make[2]: Entering directory `/home/rob/qpidc-0.6/bindings/qmf/ruby' > make[2]: *** No rule to make target `ruby.i', needed by `qmfengine.cpp'. > Stop. > > If I download the full source > qpid-0.6rc2.tar.gz<http://qpid.apache.org/dist/qpid-0.6rc2/qpid-0.6rc2.tar.gz>, > go to the cpp and do the ./bootstrap and then configure and make it all > builds fine > > -- Rob > > 2009/12/22 Andrew Stitcher <[email protected]> > > I've now respun 0.6 and there will shortly be a qpid-0.6rc2 release for >> your delectation at: >> >> http://qpid.apache.org/dist/qpid-0.6rc2 >> >> This respin includes QPID-2239, QPID-2240, QPID-2296. >> >> Please check it out, test it, read the accompanying text files etc. >> At this point I'm really only intending to allow blocker bug fixes, but >> please raise the bug and assign to me first before commiting the change >> to trunk. >> >> The other change I expect is changes to the release note files, but I >> need help there to produce new text for them. >> >> Andrew >> >> On Tue, 2009-12-22 at 13:05 -0500, Andrew Stitcher wrote: >> > I'm going to respin 0.6 (to give rc2). I'll do this either last thing >> > today or first thing tomorrow. >> > >> > This is warning that you've got a few hours to find more critical >> > problems before the respin. >> > >> > Once I've spun rc2 I'll be enforcing blocker only more seriously. >> > >> > I know that many people won't be working next week (including me) so I'd >> > really appreciate whatever time people can use today/tomorrow to look at >> > the rc1 or rc2 when it's out. >> > >> > The current issues are in the C++ cluster code and the dotnet (not WCF) >> > client so any problems in other areas should be common to be rc1/rc2 at >> > present. >> > >> > Andrew >> > >> > >> > --------------------------------------------------------------------- >> > Apache Qpid - AMQP Messaging Implementation >> > Project: http://qpid.apache.org >> > Use/Interact: mailto:[email protected] >> > >> >> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> >
