Thanks Glenn, I'll give it a try (I assumed the build download was 32 bit). regards, Aidan

Ahh just realised you're running on i686 (32 bit) whereas the binary is built for x86_64 (64 bit). If you download the source and build from scratch it will be OK. Source for the 2.1 release is

Hi Glenn, I get the following: bash-3.2$ make -f Makefile.sample .mamalistencpp g++ -I../../..//include -c -o mamalistencpp.o mamalistencpp.cpp g++ -I../../..//include -rdynamic -L../../..//lib

Hi Aidan, What error are you getting when you try to compile? I'm running on a very similar version (below), though it should work on most modern Linux distributions. 2.6.18-194.11.4.el5 #1 SMP Tue

Hi, I downloaded the OpenMAMA 2.1 Linux package, and installed. However the binaries are not compatible with the platform below, so I cannot execute the test programs, or compile a test program (lib

Hi Glenn, Thanks following up. Good news on the wire compatibility - will give me lots more integration options :-) Re: building. The README file indicates you only need to run generateBuildFiles.sh

Hi Bill, Answers below. Is OpenMama 2.x wire compatible with 1.x? I'd like to run a Java 2.x subscriber and be able to pick up either 1.x or 2.x messages. Yes. The wire level protocols are defined

Hi, I've just picked up OpenMama 2.x and I've a few questions if I may (I tried #openmama, but all's quiet there)... Is OpenMama 2.x wire compatible with 1.x? I'd like to run a Java 2.x subscriber

Hi Frank, We do have a null bridge implementation which would be prototype for anyone interested to write bridge to the OpenMAMA, Will are also working on the null payload bridge implementation. The

Hi Folks, I can see the Bridge and Payload is nicely separated in the C code, but there is some code in there which I'm not certain is required for just the bridge implementation as opposed to for the

Hey All, We are delighted to announce the release of the OpenMDM Phase 2 Equities and Indices Consultation documentation which shall be published over the next week. In this first documentation

I pushed a number of changes to the git repository this week, and created two new branches. The new branches are "next" and OpenMama-2.1.1. The next branch contains all the patches submitted to the

The wmw middleware should be build in the API and Feedhandler, you should be fine with demo kit. Jacob From: John Gray <john.gray@...> Date: Friday, June 8, 2012 11:26 AM To: Jacobraj Benet

Do you have libstdc++ installed? You can check in the synaptic package manager. Regards, -Mike

Getting there - added a symlink to /usr/lib64 for libuuid.so and that got me further... However, getting some undefined references: libtool: link: g++ -g -O2 -rdynamic -o .libs/comboticker

On what OS are you building? Where are you finding libuuid.so? I build fine with no modifications to LD_LIBRARY_PATH on Fedora 16: /lib64/libuuid.so.1 /lib64/libuuid.so.1.3.0

Apologies for resorting back again - this is probably more UNIX than mama! I can see the make files being constructed, but the examples are still not being built - and the make seems to stop before

Thanks for clarifying. The first release of the OpenMAMA was only in C and the bridge implementation was also in C and this release was expected to only work on the Avis router C implementation. In

Hi John, The configure script in openmama accepts —avis-path instead of —with-avis, so you could try the following. ./configure —avis-path=/usr/local Also if you would like the openmama-2.1 to

Hey Guys I have tried building the openmama examples - but can't get this to happen. The ./configure --with-avis=/usr/local comes back with unknown parameter --with-avis Also, the /opt/openmama files