qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Giusti <kgiu...@redhat.com>
Subject Re: Tested Linux platforms with 0.18
Date Mon, 29 Oct 2012 13:39:36 GMT
Hi Sean - sorry, I was away this weekend.

Are you building from the released packages, or are you building in an subversion or git checked-out
source repository?

If you are building from a checkout of the source tree, the managementgen.mk file is created
when you run the "bootstrap" script prior to building.  There should be a "bootstrap" script
in the cpp directory.  Specifically, you want to "cd" into the cpp directory, and type:

   ./bootstrap && ./configure && make

You only have to run bootstrap and configure once, then you can just do "make" each time you
want to rebuild.

If you are trying to build from the released tar files, then 'bootstrap' has already been
run, and that managementgen.mk file should be there already - perhaps it got deleted?  If
so, do the "untar" of the package again and see if it is present.

Let me know if that helps,


-K

----- Original Message -----
> From just looking at this:
> 
> ../managementgen/qmf-gen -m ./managementgen.mk -c
> ./managementgen.cmake -q -b -o qmf ../../specs/management-schema.xml
> ./qpid/acl/management-schema.xml ./qpid/cluster/management-schema.xml
> ./qpid/ha/management-schema.xml
> : No such file or directory
> make[1]: *** [managementgen.mk] Error 127
> 
> 
> From the qpid/cpp/src, all these files exists EXCEPT for
> managementgen.cmake
> 
> Is that a file that should be generated by the script
> ./managementgen/qmf-gen?
> 
> How can I  debug this qmf-gen script?
> 
> 
> 
> 
> On Fri, Oct 26, 2012 at 2:46 PM, Sean K <sk92129@gmail.com> wrote:
> > Oops.   I was looking at an old error that I already resolved.
> >
> > Here is the correct error with 'make'
> >
> >
> > Skipped ./qpid/framing/ClusterConnectionQueueFairshareStateBody.cpp
> > - unchanged
> > Skipped ./qpid/framing/ClusterConnectionQueueObserverStateBody.h -
> > unchanged
> > Skipped ./qpid/framing/ClusterConnectionQueueObserverStateBody.cpp
> > - unchanged
> > Skipped ./qpid/framing/ClusterConnectionClockBody.h - unchanged
> > Skipped ./qpid/framing/ClusterConnectionClockBody.cpp - unchanged
> > Skipped
> > ./qpid/framing/ClusterConnectionQueueDequeueSincePurgeStateBody.h
> > - unchanged
> > Skipped
> > ./qpid/framing/ClusterConnectionQueueDequeueSincePurgeStateBody.cpp
> > - unchanged
> > Skipped ./qpid/framing/ClusterConnectionInternalStateBody.h -
> > unchanged
> > Skipped ./qpid/framing/ClusterConnectionInternalStateBody.cpp -
> > unchanged
> > Skipped ../include/qpid/framing/amqp_structs.h - unchanged
> > Skipped ./qpid/amqp_0_10/exceptions.h - unchanged
> > Skipped ./tests/allSegmentTypes.h - unchanged
> > Skipped ./qpid/amqp_0_10/TypeForCode.h - unchanged
> > Skipped ./qpid/amqp_0_10/TypeForCode.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/CodeForType.h - unchanged
> > Skipped ./qpid/amqp_0_10/CodeForType.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/specification_fwd.h - unchanged
> > Skipped ./qpid/amqp_0_10/specification.h - unchanged
> > Skipped ./qpid/amqp_0_10/specification.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/ProxyTemplate.h - unchanged
> > Skipped ./qpid/amqp_0_10/structs.h - unchanged
> > Skipped ./qpid/amqp_0_10/structs.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/CommandHolder.h - unchanged
> > Skipped ./qpid/amqp_0_10/CommandHolder.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/CommandVisitor.h - unchanged
> > Skipped ./qpid/amqp_0_10/ApplyCommand.h - unchanged
> > Skipped ./qpid/amqp_0_10/ControlHolder.h - unchanged
> > Skipped ./qpid/amqp_0_10/ControlHolder.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/ControlVisitor.h - unchanged
> > Skipped ./qpid/amqp_0_10/ApplyControl.h - unchanged
> > Skipped ./qpid/amqp_0_10/StructHolder.h - unchanged
> > Skipped ./qpid/amqp_0_10/StructHolder.cpp - unchanged
> > Skipped ./qpid/amqp_0_10/StructVisitor.h - unchanged
> > Skipped ./qpid/amqp_0_10/ApplyStruct.h - unchanged
> > Skipped ./qpid/amqp_0_10/handlers.h - unchanged
> > ../managementgen/qmf-gen -m ./managementgen.mk -c
> > ./managementgen.cmake -q -b -o qmf
> > ../../specs/management-schema.xml
> > ./qpid/acl/management-schema.xml
> > ./qpid/cluster/management-schema.xml
> > ./qpid/ha/management-schema.xml
> > : No such file or directory
> > make[1]: *** [managementgen.mk] Error 127
> > make[1]: Leaving directory `/home/sean/qpid/qpid-0.18/cpp/src'
> > make: *** [all-recursive] Error 1
> >
> >
> >
> >
> >
> > On Fri, Oct 26, 2012 at 2:30 PM, Sean K <sk92129@gmail.com> wrote:
> >> Sure..
> >>
> >> checking if libtool supports shared libraries... yes
> >> checking whether to build shared libraries... yes
> >> checking whether to build static libraries... no
> >> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
> >> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld...
> >> yes
> >> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64)
> >> supports
> >> shared libraries... yes
> >> checking for g++ option to produce PIC... -fPIC -DPIC
> >> checking if g++ PIC flag -fPIC -DPIC works... yes
> >> checking if g++ static flag -static works... no
> >> checking if g++ supports -c -o file.o... yes
> >> checking if g++ supports -c -o file.o... (cached) yes
> >> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64)
> >> supports
> >> shared libraries... yes
> >> checking dynamic linker characteristics... GNU/Linux ld.so
> >> checking how to hardcode library paths into programs... immediate
> >> checking for library containing dlopen... -ldl
> >> checking for library containing clock_gettime... -lrt
> >> checking for clock_gettime... yes
> >> checking for clock_settime... yes
> >> checking for valgrind... valgrind
> >> checking for rpmlint... no
> >> checking for ruby... ruby
> >> checking for swig... no
> >> configure: WARNING: cannot find 'swig' program. You should look at
> >> http://www.swig.org
> >> checking for ruby1.8... no
> >> checking for ruby... /usr/bin/ruby
> >> checking for python... /usr/bin/python
> >> checking for python version... 2.6
> >> checking for python platform... linux2
> >> checking for python script directory...
> >> ${prefix}/lib/python2.6/site-packages
> >> checking for python extension module directory...
> >> ${exec_prefix}/lib64/python2.6/site-packages
> >> checking for pkg-config... /usr/bin/pkg-config
> >> checking pkg-config is at least version 0.9.0... yes
> >> checking for PYTHON... no
> >> configure: WARNING: Didn't find Python 2.7 developer libs -
> >> looking
> >> for older version
> >> checking for Py_Initialize in -lpython2.6... no
> >> checking for "/usr/include/python2.6/Python.h"... no
> >> configure: WARNING: Couldn't find Python developer libs - you
> >> probably
> >> don't have a python-dev or python-devel package installed
> >> checking for perl... perl
> >> checking for "/usr/lib64/perl5/CORE/perl.h"... yes
> >> checking boost/shared_ptr.hpp usability... yes
> >> checking boost/shared_ptr.hpp presence... yes
> >> checking for boost/shared_ptr.hpp... yes
> >> checking uuid/uuid.h usability... no
> >> checking uuid/uuid.h presence... no
> >> checking for uuid/uuid.h... no
> >> configure: error: Missing required header files.
> >>
> >>
> >> Based on this last check that was done, I ensured that
> >>
> >> libuuid-devel
> >> e2fsprogs-devel
> >>
> >> were installed using "sudo yum install libuuid-devel
> >> e2fsprogs-devel"
> >>
> >> They were installed, or i installed them, and I re-tried the
> >> 'make',
> >> it still failed right after the uuid.h not being found.
> >>
> >> Then I looked at the configure --help output if I can directly
> >> tell
> >> configure where to look for the uuid.h or that package, but I
> >> couldnt
> >> figure that out -- not without reading the whole configure or make
> >> script.
> >>
> >> Hopefully this sheds more light on my situation.
> >>
> >>
> >> On Fri, Oct 26, 2012 at 1:47 PM, Ken Giusti <kgiusti@redhat.com>
> >> wrote:
> >>> Hi Sean,
> >>>
> >>> Like Darryl, I do most of my qpid work using the latest Fedora.
> >>>   However, I was able to build the latest stable branch of qpid
> >>> (0.18) successfully on my Centos 6 x86_64 machine (fully up to
> >>> date).
> >>>
> >>> Can you cut and paste your build errors into an email?
> >>>
> >>> thanks,
> >>>
> >>> -K
> >>>
> >>> ----- Original Message -----
> >>>> Hi
> >>>>
> >>>> I am looking for which linux platforms has been tested with the
> >>>> CPP
> >>>> broker, in terms of successfully building and running.
> >>>>
> >>>>
> >>>> cat on /etc/centos-release shows this:
> >>>> Linux centos-test1 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22
> >>>> 12:19:21
> >>>> UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
> >>>>
> >>>> I have spent 1 hour with centos 6.3 64 bit and have run into
> >>>> 'make'
> >>>> problems, which I have not found solutions on the jira or on the
> >>>> wiki.
> >>>>
> >>>>
> >>>> So, I thought I had better use a linux specific version (and
> >>>> whether
> >>>> 64 or 32 bit) and spend my time learning qpid on that linux
> >>>> platform.
> >>>>
> >>>> Since I am using vmware to run the linux, I figure it should be
> >>>> fast
> >>>> to switch to another linux platform before I dive into a
> >>>> time-sink.
> >>>>
> >>>> ---------------------------------------------------------------------
> >>>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> >>>> For additional commands, e-mail: users-help@qpid.apache.org
> >>>>
> >>>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> >>> For additional commands, e-mail: users-help@qpid.apache.org
> >>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
> For additional commands, e-mail: users-help@qpid.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


Mime
View raw message