[rabbitmq-discuss] Fwd: compatibility with legacy code

[Jim Irrer]

Forgot to CC the discussion group.


---------- Forwarded message ----------
From: Jim Irrer <irrer at umich.edu>
Date: Wed, Nov 4, 2009 at 3:05 PM
Subject: Re: [rabbitmq-discuss] compatibility with legacy code
To: tonyg at lshift.net
Cc: David Wragg <david.wragg at lshift.net>, Jim Irrer <irrer at umich.edu>


Tony -

David Wragg suggested I try your C interface to RabbitMQ.  I did, and
got the following build (running on Ubuntu 2.6.28-15) error below.  Does
this
mean that the package is missing the *amqp-0.9.1.json* file?

Also, I was using rabbitmq-c-06125761fef6.tar.gz from
http://hg.rabbitmq.com/ .

irrer-ubuntu:autoreconf -i ; echo $?
libtoolize: putting auxiliary files in `.'.
libtoolize: copying file `./config.guess'
libtoolize: copying file `./config.sub'
libtoolize: copying file `./install-sh'
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and
libtoolize: rerunning libtoolize, to keep the correct libtool macros
in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
configure.ac:3: installing `./missing'
examples/Makefile.am: installing `./depcomp'
0
irrer-ubuntu:./configure ; echo $?
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries...
yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for ANSI C header files... (cached) yes
checking location of AMQP codegen directory... configure: error: could not
find AMQP spec file at "'/home/irrer/utilitie
s/rabbitmq/rabbitmq-c/rabbitmq-c-06125761fef6/codegen/amqp-0.9.1.json'"


Jim Irrer     irrer at umich.edu       (734) 647-4409
University of Michigan Hospital Radiation Oncology
519 W. William St.             Ann Arbor, MI 48103


On Wed, Nov 4, 2009 at 11:24 AM, David Wragg <david.wragg at lshift.net> wrote:

> Hi Jim,
>
> Jim Irrer <irrer at umich.edu> writes:
> > We are starting to use RabbitMQ but need to connect to
> > a legacy application written in C/C++ (about 2 million lines
> > of code).  Does anyone have any suggestions or experience
> > on how to do this?
>
> There's a C client for rabbitmq at
> <http://hg.rabbitmq.com/rabbitmq-c/>.  It's marked as experimental,
> but I think it's seen some real-world use already.  If you take a
> look, I'm sure Tony would be interested in any feedback you have.
>
> David
>
> --
>  [][][] David Wragg       | mail: david.wragg at lshift.net
>   [][] Senior Developer  | tel: +44 (0)20 7729 7060
>  []  [] LShift Ltd        | web: www.lshift.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20091105/0a339e38/attachment.htm