issue starting ardour3

billbrown · 2013-05-30 14:23:56

Hello.

I'm not sure if my path is messed up or there is something missing from my environment but after installing ardour-3.1-1, it doesn't start form the command line with the executable in the path.

[bill@billbrown ~]$ ardour3
-bash: /usr/local/bin/ardour3: No such file or directory

Once I made symbolic link from /usr/bin/ardour3 to /usr/local/bin/ardour3 the program starts.

Is this a packaging issue or maybe something I have setup incorrectly in my environment?

Thanks.

karol · 2013-05-30 17:32:40

I've just installed the 32-bit package and it works fine.
Are you using the package from the repos, some AUR package or ...?

Run 'less /usr/bin/ardour3' to view that file.

billbrown · 2013-05-30 18:01:29

OK. I installed the x86_64 package of ardour-3.1.1 from the extra repo.

here is the contents of the script /usr/bin/ardour3

#!/bin/sh

#
# This script runs an installed version of Ardour. It sets a few environment var
iables
# and does a few checks before exec'ing the real executable.
# 

export GTK_PATH=/etc/ardour3:/usr/lib/ardour3${GTK_PATH:+:$GTK_PATH}

export LD_LIBRARY_PATH=/usr/lib/ardour3${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}

## Memlock check

MLOCK_LIMIT=$(ulimit -l)
if [ "$MLOCK_LIMIT" != "unlimited" ]; then
        echo "WARNING: Your system has a limit for maximum amount of locked memo
ry!"
        echo "         This might cause Ardour to run out of memory before your 
system runs"
        echo "         out of memory. You can view the memory limit with 'ulimit
 -l', and it"
        echo "         is normally controlled by /etc/security/limits.conf"
        echo ""

fi

## Glib atomic test

GLIB=$(ldd /usr/lib/ardour3/ardour-3.0 2> /dev/null | grep glib-2.0 | sed 's/.*=
> \([^ ]*\) .*/\1/')

if [ "$GLIB" = "" ]; then
        echo "WARNING: Could not check your glib-2.0 for mutex locking atomic op
erations."
        echo ""
elif [ $(nm -D --radix=dec --defined-only -S $GLIB | grep -w g_atomic_int_add | 
cut -d ' ' -f 2) -gt 32 ]; then
        echo "WARNING: Your system contains a suspect libglib-2.0. Your version 
might be built"
        echo "         to use mutex locking atomic operations. This is a fallbac
k solution to"
        echo "         a more robust hardware supported atomicity. It might caus
e reduced "
        echo "         performance and/or deadlocks. Please contact your distrib
ution support"
        echo "         about this issue."
        echo "         Unfortunately this check is not 100% accurate, so this mi
ght not be"
        echo "         the case with your system."
        echo ""
fi

#
# Running Ardour requires these 3 variables to be set
#

export ARDOUR_DATA_PATH=/usr/share/ardour3
export ARDOUR_CONFIG_PATH=/etc/ardour3
export ARDOUR_DLL_PATH=/usr/lib/ardour3

#
# VAMP has its own lookup path
# 

export VAMP_PATH=/usr/lib/ardour3/vamp

if [ $# -gt 0 ] ; then
    case $1 in
        -g|--gdb) GDB=gdb; shift ;;
    esac
fi

exec $GDB /usr/lib/ardour3/ardour-3.0 "$@"

I don't see /usr/local listed anywhere in the script so I'm confused why this script is trying to call "/usr/local/bin/ardour3"

thanks for anymore advice.

Arch Linux

#1 2013-05-30 14:23:56

issue starting ardour3

#2 2013-05-30 17:32:40

Re: issue starting ardour3

#3 2013-05-30 18:01:29

Re: issue starting ardour3

Board footer