[rabbitmq-discuss] erlang client blowing chunks
jon.brisbin at npcinternational.com
Wed Sep 1 16:46:20 BST 2010
On Sep 1, 2010, at 10:16 AM, Vlad Alexandru Ionescu wrote:
> On 09/01/2010 04:11 PM, Jon Brisbin wrote:
>> make run_test_broker RUN_TEST_BROKER_ARGS="-s network_client_SUITE test"
>> make -C ../rabbitmq-server start-background-node
>> RABBITMQ_NODE_IP_ADDRESS="" RABBITMQ_NODE_PORT="" RABBITMQ_LOG_BASE="/var/folders/+E/+EAa1V61EkOEVs83Nv6vbU+++TI/-Tmp-/" RABBITMQ_MNESIA_DIR="/var/folders/+E/+EAa1V61EkOEVs83Nv6vbU+++TI/-Tmp-//rabbitmq-rabbit-mnesia" \
>> RABBITMQ_NODE_ONLY=true \
>> RABBITMQ_SERVER_START_ARGS=" -detached" \
>> ./scripts/rabbitmq-server ; sleep 1
>> make -C ../rabbitmq-server start-rabbit-on-node
>> echo "rabbit:start()." | erl_call -sname rabbit -e
>> /bin/sh: erl_call: command not found
>> make: *** [start-rabbit-on-node] Error 127
>> make: *** [boot_broker] Error 2
>> make: *** [test_network] Error 2
> No, this is a /completely/ different error :) .
> That means you don't have erl_call in your path. It is usually under $ERL_TOP/lib/erl_interface-3.7/bin (version may vary). You have to add that to your PATH env var.
Sorry for not being clear. I meant that either checking out the umbrella and updating the Makefile to use the 2.0 tag or checking the three dependent projects individually using the same tag results in the same build failure. I didn't mean to say that this error was related to the problem connecting to a 2.0 broker. I'm getting hasty today. :)
Either way, I was not able to successfully build the erlang client and use it to connect to a 2.0 broker (installed using the rabbitmq apt repository) on my Linux box from a standalone OTP application.
NPC International, Inc.
More information about the rabbitmq-discuss