You are not logged in.
Pages: 1
I'm just wondering what the status of the ardour package is. I know that there are issues with the latest gcc versions...is that whats holding it up? Is it being actively maintained? Mind you this is not a complaint post. I am aware that people donate time and energy here, have lives, and are generally busy....so please save the "when its does" comments
Thanks!
Offline
I compiled ardour 2.4.1 last week using ABS.
There's something wrong with scons checking if boost is installed (i have no idea why it doesn't work and i haven't learned to debug python code yet). It was discussed on ardour forums [1], but without a working solution. I commented out part of the SConstruct file as a workaround.
http://nopaste.org/p/aknjljPFH
(don't forget the last line - it contains only one space)
The Bad Thing is that I found this patch [2] after I had lost few hours to create my own.
[1] http://ardour.org/node/587
[2] http://tracker.ardour.org/view.php?id=2181
Last edited by slepy (2008-05-21 08:10:41)
Offline
Hi Slepy, any chance you could paste up your PKGBUILD? Is that the only patch you needed to apply?
Offline
This is me . I created new forum account.
I tried to use the patch provided in the ardour bugtracker but it failed (!), so here is PKGBUILD with my patches.
http://hoth.amu.edu.pl/~j_roszkowski/ardour24.tar.gz
Should I upload it to AUR? This is basically the same package as in extra with version bumped and patch to make it work so it will become obsolete once the official package gets updated.
Last edited by j.roszk (2008-05-22 13:52:28)
Offline
No, you shouldn't upload it to the AUR as it is against the AUR policy. I don't know how long this has been flagged out of date for but if it has been a while you could send a polite email to the maintainer with a link to your patch (and the official patch you mention above).
Offline
Ok the deal with ardour is its internal libs..as you may or may not know using external is not supported by ardour and is a pain in itself. Arch's ardour update will be a while longer, because the gcc 4.3 patch is not enough due to the internal libsigc problem. Just yesterday (or today depending on where you are) there was a libsigc svn commit for 2.0 ongoing and it is said that everything should be back to normal. Not quite sure about any other build problems but here's the vst pkgbuild I stopped writing after libsigc++ didn't compile
pkgname=ardourvst
_pkgname=ardour
pkgver=2.4.1
pkgrel=1
pkgdesc="A multichannel hard disk recorder and digital audio workstation (with Windows VST support)"
arch=(i686)
license=('GPL')
url="http://ardour.org"
depends=('liblrdf>=0.4.0-5' 'libsamplerate' 'jack-audio-connection-kit' 'flac'
'curl>=7.16.2' 'libart-lgpl' 'ladspa' 'libxslt' 'libgnomecanvas'
'liblo' 'libusb' 'fftw' 'wine' 'steinberg-vst')
makedepends=('librsvg' 'scons' 'boost' 'zip')
conflicts=('ardour')
install=${pkgname}.install
source=(http://ardour.org/files/releases/${_pkgname}-${pkgver}.tar.bz2
${pkgname}.desktop
libsndfile.patch
${_pkgname}-2.4-gcc43.patch)
build() {
# copy vst headers; we don't want to rewrite python code
[ -d "${startdir}/vst" ] || {
echo "Please copy /usr/include/vst to working directory:"
echo
echo "$startdir"
return 1
}
# fix building with gcc 4.3
cd ${startdir}/src/${_pkgname}-${pkgver}
patch -Np1 -i ../${_pkgname}-2.4-gcc43.patch
# start building ardour now
patch -Np1 -i ../libsndfile.patch || return 1
sed -i -e "s@/configure@& --prefix=/usr@g" libs/libsndfile/SConscript
sed -i -e "s/lib64/lib/g" SConstruct
sed -i -e "s:usr/local:usr:g" SConstruct
# ardour has no option to use existing vst headers
sed -i -e \
"s:vstsdk2.3/source/common/aeffectx.h:/usr/include/vst/aeffectx.h:g" \
libs/fst/SConscript
_vstdir="vstsdk2.3/source/common"
mkdir -p $_vstdir
cp -r ${startdir}/vst/./ $_vstdir
# someone please sub this with a bsdtar equivalent
zip -0r libs/fst/vstsdk2.3.zip vstsdk2.3 &> /dev/null
# force -O2 from the CFLAGS in makepkg.conf
sed -i '/-O3/d' SConstruct
# no slv2-svn package yet; no LV2
scons ARCH="${CFLAGS}" \
FREESOUND=1 \
LV2=0 \
VST=1 \
PREFIX="/usr" \
DESTDIR="${startdir}/pkg" || return 1
scons PREFIX="/usr" \
DESTDIR="${startdir}/pkg" \
install || return 1
# we may want ardourvst renamed but until we manage to compile..
# =p >( !!!#$%#$^&^$&
# install some freedesktop.org compatibility
install -D -m644 ${startdir}/src/${pkgname}.desktop \
${startdir}/pkg/usr/share/applications/${pkgname}.desktop
}
As for Arch binary update from extra, I don't know when the next upstream update is coming but it will soon, and when it does just knock on tobias (email in abs pkgbuild).
Last edited by schivmeister (2008-05-24 04:30:36)
I need real, proper pen and paper for this.
Offline
I don't know if my patch resolves the "internal libsigc problem", but it surely make it compile, so you might want to try mine (it's in the tarball) with your ardourvst package. My binary is compiled with vst as well, but i removed this stuff from PKGBUILD to make it almost the same as the one gained from ABS.
And there is nothing about looking for boost headers in your PKGBUILD. Does the default SConstruct file work for you?
Offline
Yep thanks, I've downloaded your tarball. It looks like I was mistaken about libsigc, it's included in your copy of the gcc patch but not in mine (downloaded from ardour mantis). Where did you get it from? I'm not facing any boost issue though, but it's still building.
edit: this patch works..if i understand correctly from the posts above, it's re-written/merged with new changes right? If so, post it in mantis and notify them. And yes, I didn't need the boost patch. We should nudge tobias now
Last edited by schivmeister (2008-05-24 04:30:59)
I need real, proper pen and paper for this.
Offline
I made it myself with these guidelines. It wasn't hard at all - only boring I haven't posted it yet on the bugtracker, because I thought the problem might be Arch-specific (since their patch is said to fix problems), but I will do it soon.
Last edited by j.roszk (2008-05-24 06:30:43)
Offline
I got ardour to build. Strange thing is that it builds in quarter the time it usually takes to build it and it doesn't run:
# ardour2
/usr/bin/ardour2: line 16: /usr/lib/ardour2/ardour-2.4.1: No such file or directory
/usr/bin/ardour2: line 16: exec: /usr/lib/ardour2/ardour-2.4.1: cannot execute: No such file or directory
I've tried to rebuild it many times but same error after installing.
Last edited by funkmuscle (2008-05-25 23:40:54)
Offline
I don't know why does it happen to you. I have built and installed my package today to check it and it contains this file.
$ pacman -Ql ardour | grep ardour-2.4.1
ardour /usr/lib/ardour2/ardour-2.4.1
Offline
it compiles, installs but the same error. this is a fresh install of arch and running no crazy test packages. Does anyone know why it builds so fast? I have an athlon 1.7 with 1gb ram. usually ardour takes 40+ minutes to compile. now it takes 10 minutes... I get no error messages..
/usr/bin/ardour2: line 16: /usr/lib/ardour2/ardour-2.4.1: No such file or directory
/usr/bin/ardour2: line 16: exec: /usr/lib/ardour2/ardour-2.4.1: cannot execute: No such file or directory
same crap with ardour 3. I installed in a different directory but same issues.
$ /usr/local/bin/ardour3
/usr/local/bin/ardour3: line 18: /usr/local/lib/ardour3/ardour-3.0: No such file or directory
/usr/local/bin/ardour3: line 18: exec: /usr/local/lib/ardour3/ardour-3.0: cannot execute: No such file or directory
I had ardour running before my system crashed. I compiled the same ardour-2.4.1 came out. never an issue with boost, gcc(had old version)..
could this be the cause?:
scons: warning: The env.Copy() method is deprecated; use the env.Clone() method instead.
File "/home/yer/apps/ardour24/src/ardour-2.4.1/libs/sigc++2/SConscript", line 10, in <module>
Yeah, it was scons...rolled back to an earlier version and Ardour compiled and took like 50 minutes to do so and it installed and running.
Last edited by funkmuscle (2008-05-30 04:28:57)
Offline
This package is now very out-of-date again. The current Arch version is 2.5-1, and the current release is 2.7. Does anyone know that's going on with this? It's been flagged for a while now. I've never had any luck building Ardour from source, so I'm hoping someone less-noobish than me will take it up.
Offline
yeah, this should of been marked solved as yes, 2.7 was just released and I'm running it.
Offline
Pages: 1