Forgot to CC the discussion group.<br>
<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Jim Irrer</b> <span dir="ltr"><<a href="mailto:irrer@umich.edu">irrer@umich.edu</a>></span><br>Date: Wed, Nov 4, 2009 at 3:05 PM<br>
Subject: Re: [rabbitmq-discuss] compatibility with legacy code<br>To: <a href="mailto:tonyg@lshift.net">tonyg@lshift.net</a><br>Cc: David Wragg <<a href="mailto:david.wragg@lshift.net">david.wragg@lshift.net</a>>, Jim Irrer <<a href="mailto:irrer@umich.edu">irrer@umich.edu</a>><br>
<br><br>Tony -<br><br>David Wragg suggested I try your C interface to RabbitMQ. I did, and<br>got the following build (running on Ubuntu 2.6.28-15) error below. Does this<br>mean that the package is missing the <b><i>amqp-0.9.1.json</i></b> file?<br>
<br>Also, I was using rabbitmq-c-06125761fef6.tar.gz from <a href="http://hg.rabbitmq.com/" target="_blank">http://hg.rabbitmq.com/</a> .<br><br><div style="margin-left: 40px;">irrer-ubuntu:autoreconf -i ; echo $?<br>libtoolize: putting auxiliary files in `.'.<br>
libtoolize: copying file `./config.guess'<br>libtoolize: copying file `./config.sub'<br>libtoolize: copying file `./install-sh'<br>libtoolize: copying file `./ltmain.sh'<br>libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to <a href="http://configure.ac" target="_blank">configure.ac</a> and<br>
libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.<br>libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.<br><a href="http://configure.ac:3" target="_blank">configure.ac:3</a>: installing `./missing'<br>
examples/Makefile.am: installing `./depcomp'<br>0<br>irrer-ubuntu:./configure ; echo $?<br>checking for a BSD-compatible install... /usr/bin/install -c<br>checking whether build environment is sane... yes<br>checking for a thread-safe mkdir -p... /bin/mkdir -p<br>
checking for gawk... no<br>checking for mawk... mawk<br>checking whether make sets $(MAKE)... yes<br>checking for gcc... gcc<br>checking for C compiler default output file name... a.out<br>checking whether the C compiler works... yes<br>
checking whether we are cross compiling... no<br>checking for suffix of executables...<br>checking for suffix of object files... o<br>checking whether we are using the GNU C compiler... yes<br>checking whether gcc accepts -g... yes<br>
checking for gcc option to accept ISO C89... none needed<br>checking for style of include used by make... GNU<br>checking dependency style of gcc... gcc3<br>checking build system type... i686-pc-linux-gnu<br>checking host system type... i686-pc-linux-gnu<br>
checking for a sed that does not truncate output... /bin/sed<br>checking for grep that handles long lines and -e... /bin/grep<br>checking for egrep... /bin/grep -E<br>checking for fgrep... /bin/grep -F<br>checking for ld used by gcc... /usr/bin/ld<br>
checking if the linker (/usr/bin/ld) is GNU ld... yes<br>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B<br>checking the name lister (/usr/bin/nm -B) interface... BSD nm<br>checking whether ln -s works... yes<br>
checking the maximum length of command line arguments... 1572864<br>checking whether the shell understands some XSI constructs... yes<br>checking whether the shell understands "+="... yes<br>checking for /usr/bin/ld option to reload object files... -r<br>
checking for objdump... objdump<br>checking how to recognize dependent libraries... pass_all<br>checking for ar... ar<br>checking for strip... strip<br>checking for ranlib... ranlib<br>checking command to parse /usr/bin/nm -B output from gcc object... ok<br>
checking how to run the C preprocessor... gcc -E<br>checking for ANSI C header files... yes<br>checking for sys/types.h... yes<br>checking for sys/stat.h... yes<br>checking for stdlib.h... yes<br>checking for string.h... yes<br>
checking for memory.h... yes<br>checking for strings.h... yes<br>checking for inttypes.h... yes<br>checking for stdint.h... yes<br>checking for unistd.h... yes<br>checking for dlfcn.h... yes<br>checking for objdir... .libs<br>
checking if gcc supports -fno-rtti -fno-exceptions... no<br>checking for gcc option to produce PIC... -fPIC -DPIC<br>checking if gcc PIC flag -fPIC -DPIC works... yes<br>checking if gcc static flag -static works... yes<br>
checking if gcc supports -c -o file.o... yes<br>checking if gcc supports -c -o file.o... (cached) yes<br>checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes<br>checking whether -lc should be explicitly linked in... no<br>
checking dynamic linker characteristics... GNU/Linux ld.so<br>checking how to hardcode library paths into programs... immediate<br>checking whether stripping libraries is possible... yes<br>checking if libtool supports shared libraries... yes<br>
checking whether to build shared libraries... yes<br>checking whether to build static libraries... yes<br>checking for ANSI C header files... (cached) yes<br>checking location of AMQP codegen directory... configure: error: could not find AMQP spec file at "'/home/irrer/utilitie<br>
s/rabbitmq/rabbitmq-c/rabbitmq-c-06125761fef6/codegen/amqp-0.9.1.json'"<br></div><div class="im"><br><br clear="all">Jim Irrer <a href="mailto:irrer@umich.edu" target="_blank">irrer@umich.edu</a> (734) 647-4409<br>
University of Michigan Hospital Radiation Oncology<br>
519 W. William St. Ann Arbor, MI 48103<br>
<br><br></div><div><div></div><div class="h5"><div class="gmail_quote">On Wed, Nov 4, 2009 at 11:24 AM, David Wragg <span dir="ltr"><<a href="mailto:david.wragg@lshift.net" target="_blank">david.wragg@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Jim,<br>
<div><br>
Jim Irrer <<a href="mailto:irrer@umich.edu" target="_blank">irrer@umich.edu</a>> writes:<br>
> We are starting to use RabbitMQ but need to connect to<br>
> a legacy application written in C/C++ (about 2 million lines<br>
> of code). Does anyone have any suggestions or experience<br>
> on how to do this?<br>
<br>
</div>There's a C client for rabbitmq at<br>
<<a href="http://hg.rabbitmq.com/rabbitmq-c/" target="_blank">http://hg.rabbitmq.com/rabbitmq-c/</a>>. It's marked as experimental,<br>
but I think it's seen some real-world use already. If you take a<br>
look, I'm sure Tony would be interested in any feedback you have.<br>
<br>
David<br>
<font color="#888888"><br>
--<br>
[][][] David Wragg | mail: <a href="mailto:david.wragg@lshift.net" target="_blank">david.wragg@lshift.net</a><br>
[][] Senior Developer | tel: +44 (0)20 7729 7060<br>
[] [] LShift Ltd | web: <a href="http://www.lshift.net" target="_blank">www.lshift.net</a><br>
</font></blockquote></div><br>
</div></div></div><br>